EON Steel: fix uninitialized field cache entries
EON Steel: fix uninitialized field cache entries

The check for whether we had initialized a field in the EON Steel cache
data structure was wrong, causing some entries to be returned
successfully even if their field had never been initialized.

In most cases, it didn't matter, since the cache data was initialized to
zero (which is a fine default for uninitialized data), so most of the
time it didn't matter.

But for the recently added dive mode field, this caused OC dives to be
returned as freedives, for example.

Signed-off-by: Linus Torvalds <69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org>
Signed-off-by: Dirk Hohndel <a00b27378a09822d5638cdfb8c2e7ccc36d74c56@hohndel.org>

henrik242/libdivecomputer,glance-/libdivecomputer,henrik242/libdivecomputer,Poltsi/libdivecomputer-vms,glance-/libdivecomputer