b13ba381ca
There's no way for the macio_nvram device to report failure to write data, but we can at least report it to the user with error_report() as we do in other devices like xlnx-efuse. Spotted by Coverity. Resolves: Coverity CID 1507628 Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Reviewed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Message-id: 20240312183810.557768-6-peter.maydell@linaro.org |
||
---|---|---|
.. | ||
chrp_nvram.c | ||
ds1225y.c | ||
eeprom93xx.c | ||
eeprom_at24c.c | ||
fw_cfg-acpi.c | ||
fw_cfg-interface.c | ||
fw_cfg.c | ||
Kconfig | ||
mac_nvram.c | ||
meson.build | ||
npcm7xx_otp.c | ||
nrf51_nvm.c | ||
spapr_nvram.c | ||
trace-events | ||
trace.h | ||
xlnx-bbram.c | ||
xlnx-efuse-crc.c | ||
xlnx-efuse.c | ||
xlnx-versal-efuse-cache.c | ||
xlnx-versal-efuse-ctrl.c | ||
xlnx-zynqmp-efuse.c |