diff options
author | Leah Rowe <leah@libreboot.org> | 2023-01-28 22:14:35 +0000 |
---|---|---|
committer | Leah Rowe <leah@libreboot.org> | 2023-01-28 22:14:35 +0000 |
commit | 257eedca0c729ae7341733306bc87d29b8113c28 (patch) | |
tree | 0f34c1bbde02003609a32ffbd62033ebea686c60 /resources/coreboot/x60_16mb/config/libgfxinit_txtmode | |
parent | adc76e38140e29526131d35f2c102009bfafeff8 (diff) |
util/nvmutil: reset errno if any write attempted
the way nvmutil is designed, setWord() is only ever called
under non-error conditions. however, if one part is valid but
the other one isn't, and a command is run that touches both parts,
errno is non-zero write writeGbeFile is called
in situations where one part is valid, but the other isn't, AND the
writes to gbe (in memory) results in a non-change, writeGbeFile is
not called; in this situation, errno is not being reset, despite
non-error condition
this patch fixed the bug, resulting in zero status upon exit under
such conditions
Diffstat (limited to 'resources/coreboot/x60_16mb/config/libgfxinit_txtmode')
0 files changed, 0 insertions, 0 deletions