diff options
author | Matt Fleming <[email protected]> | 2015-08-07 09:36:55 +0100 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2015-08-08 10:37:39 +0200 |
commit | 248fbcd5aee00f6519a12c5ed3bc3dc0f5e84de5 (patch) | |
tree | c3e5446c700b6224fe7ff96d7dde96b9297dcd8f /tools/perf/scripts/python/net_dropmonitor.py | |
parent | 87db73aebf55554fefaa3eade0a28f282a1511b8 (diff) |
x86/efi-bgrt: Switch pr_err() to pr_debug() for invalid BGRT
It's totally legitimate, per the ACPI spec, for the firmware to
set the BGRT 'status' field to zero to indicate that the BGRT
image isn't being displayed, and we shouldn't be printing an
error message in that case because it's just noise for users. So
swap pr_err() for pr_debug().
However, Josh points that out it still makes sense to test the
validity of the upper 7 bits of the 'status' field, since
they're marked as "reserved" in the spec and must be zero. If
firmware violates this it really *is* an error.
Reported-by: Tom Yan <[email protected]>
Tested-by: Tom Yan <[email protected]>
Signed-off-by: Matt Fleming <[email protected]>
Reviewed-by: Josh Triplett <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Matthew Garrett <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions