[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170405235304.unuljlwluw7wzktf@Haydn>
Date: Wed, 5 Apr 2017 16:53:04 -0700
From: Calvin Owens <calvinowens@...com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Petr Mladek <pmladek@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Jiri Slaby" <jslaby@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Manuel Schölling <manuel.schoelling@....de>,
Hans de Goede <hdegoede@...hat.com>,
Paul Burton <paul.burton@...tec.com>,
<linux-kernel@...r.kernel.org>, <kernel-team@...com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: [RFC][PATCH 1/2] printk: Introduce per-console filtering of
messages by loglevel
On Tuesday 04/04 at 23:27 -0400, Steven Rostedt wrote:
> On Wed, 5 Apr 2017 11:16:28 +0900
> Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> wrote:
>
>
> > one more thing.
> >
> > this per-console filtering ignores... the "ignore_loglevel" param.
> >
> > early_param("ignore_loglevel", ignore_loglevel_setup);
> > module_param(ignore_loglevel, bool, S_IRUGO | S_IWUSR);
> > MODULE_PARM_DESC(ignore_loglevel,
> > "ignore loglevel setting (prints all kernel messages to the console)");
> >
> >
> > my preference would be preserve "ignore_loglevel" behaviour. if
> > we are forced to 'ignore all loglevel filtering' then we should
> > do so.
>
> Agreed.
Makes sense, I'll add then when I resend.
Thanks,
Calvin
> -- Steve
>
Powered by blists - more mailing lists