diff options
| author | Avi Weiss <thnkslprpt@gmail.com> | 2026-08-08 22:43:47 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-08-10 17:40:51 -0700 |
| commit | 341d8aff93e2179de330c87a16be2eae0eba2ddc (patch) | |
| tree | 9d7a4b509bac3f37a65f6c2e13e7050e1e0a687f /tools/perf/scripts/python/bin/export-to-sqlite-report | |
| parent | 20232e99e8bfa44a6d77e8c3e0da2358f617e653 (diff) | |
et131x: propagate EEPROM readiness errors
eeprom_wait_ready() returns a negative error when the LBCIF status
cannot be read or the device does not become ready for some other
reason.
eeprom_write() propagates this error before starting a write, but
currently returns 0 when the same readiness check fails after the
write begins.
This behavior was introduced when the EEPROM code was refactored to
use Linux error-return conventions (from 0 = failure to 0 = success).
Return the error so callers do not treat a failed EEPROM write as
successful and the function contract is maintained.
Cc: stable+noautosel@kernel.org # untested fix to unlikely driver error path
Signed-off-by: Avi Weiss <thnkslprpt@gmail.com>
Acked-by: Mark Einon <mark.einon@gmail.com>
Link: https://patch.msgid.link/20260808194347.813242-1-thnkslprpt@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-sqlite-report')
0 files changed, 0 insertions, 0 deletions
