summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorJean Delvare <jdelvare@suse.de>2013-09-11 14:24:10 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2013-09-11 15:58:51 -0700
commitae79744975cb0b3b9c469fe1a05db37d2943c863 (patch)
tree993b12b216e4aa9b9901484d4dae83cf13c50616 /kernel
parentffbbb96dd7570b9aafd426cd77a7ee03d224cabf (diff)
downloadop-kernel-dev-ae79744975cb0b3b9c469fe1a05db37d2943c863.zip
op-kernel-dev-ae79744975cb0b3b9c469fe1a05db37d2943c863.tar.gz
firmware/dmi_scan: drop OOM messages
As reported by Joe Perches: OOM messages generally aren't useful. dmi_alloc is either a trivial front-end to kzalloc, and kzalloc already does a dump_stack() when OOM, or for x86, dmi_alloc uses extend_brk which BUGs when unsuccessful. So we can remove all 6 such log messages in the dmi_scan driver, to shrink the binary size (by 528 bytes on x86_64.) Signed-off-by: Jean Delvare <jdelvare@suse.de> Reported-by: Joe Perches <joe@perches.com> Cc: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud