aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
diff options
context:
space:
mode:
authorHans de Goede <[email protected]>2018-06-19 13:57:26 +0200
committerPetr Mladek <[email protected]>2018-06-27 16:14:29 +0200
commit22eceb8bf3e8f1f9b2f566062d06b25807725d7f (patch)
treeb4301f5587e11d78593db56fd774e93280c81400 /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
parent375899cddcbb26881b03cb3fbdcfd600e4e67f4a (diff)
printk: Make CONSOLE_LOGLEVEL_QUIET configurable
The goal of passing the "quiet" option to the kernel is for the kernel to be quiet unless something really is wrong. Sofar passing quiet has been (mostly) equivalent to passing loglevel=4 on the kernel commandline. Which means to show any messages with a level of KERN_ERR or higher severity on the console. In practice this often does not result in a quiet boot though, since there are many false-positive or otherwise harmless error messages printed, defeating the purpose of the quiet option. Esp. the ACPICA code is really bad wrt this, but there are plenty of others too. This commit makes CONSOLE_LOGLEVEL_QUIET configurable. This for example will allow distros which want quiet to really mean quiet to set CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity then KERN_ERR (CRIT, ALERT, EMERG) get printed, avoiding an endless game of whack-a-mole silencing harmless error messages. Link: http://lkml.kernel.org/r/[email protected] To: Petr Mladek <[email protected]> To: Sergey Senozhatsky <[email protected]> Cc: Hans de Goede <[email protected]> Cc: Steven Rostedt <[email protected]> Cc: [email protected] Signed-off-by: Hans de Goede <[email protected]> Acked-by: Steven Rostedt (VMware) <[email protected]> Reviewed-by: Sergey Senozhatsky <[email protected]> Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions