Attention is currently required from: Nico Huber, Sergii Dmytruk.
View Change
1 comment:
File writeprotect.c:
Patch Set #1, Line 159: new
I'm also not sure if test terminology is more appropriate here than old/new or current/new, but one […]
The key point here is that it is consistent and in keeping with the rest of the file.
In direct answer to the question - it is the 'expected bits the caller requested' and the 'actual bits observed' from the chip.
As an aside without going off in the deep end here, "new/old" doesn't really make much sense either, 'new what'. Furthermore 'new' is typically a reserved word in most languages and tends to be best avoided as a identifier for a variable.
To view, visit change 66754. To unsubscribe, or for help writing mail filters, visit settings.
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I81d2d3fc0a103ee00ced78838d77fe33a9d3056a
Gerrit-Change-Number: 66754
Gerrit-PatchSet: 2
Gerrit-Owner: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Gerrit-Reviewer: Edward O'Callaghan <quasisec@chromium.org>
Gerrit-Reviewer: Nico Huber <nico.h@gmx.de>
Gerrit-Reviewer: Nikolai Artemiev <nartemiev@google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply@coreboot.org>
Gerrit-Attention: Nico Huber <nico.h@gmx.de>
Gerrit-Attention: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Gerrit-Comment-Date: Tue, 11 Oct 2022 12:19:19 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Nico Huber <nico.h@gmx.de>
Comment-In-Reply-To: Edward O'Callaghan <quasisec@chromium.org>
Comment-In-Reply-To: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Gerrit-MessageType: comment