From: Joe Perches <joe@perches.com>
To: Peter Korsgaard <peter@korsgaard.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ttyprintk: make the printk log level configurable
Date: Fri, 07 Sep 2018 01:03:12 -0700 [thread overview]
Message-ID: <bc10850410b2c58c2bfbfa4f412403db7c82b535.camel@perches.com> (raw)
In-Reply-To: <CACXmViaj6XWUXmdFov_1-exCd5idDx2s-2_kfmDFydN75wUNNQ@mail.gmail.com>
On Fri, 2018-09-07 at 09:50 +0200, Peter Korsgaard wrote:
> On Tue, Aug 21, 2018 at 7:28 PM Peter Korsgaard <peter@korsgaard.com> wrote:
> >
> > For some use cases it is handy to use a different printk log level than the
> > default (info) for the messages written to ttyprintk, so add a Kconfig
> > option similar to what we have for default console loglevel.
>
> Ping? Feedback, comments?
I think it is moving "[U]" into TPK_LEVEL is an
unnecessary and a tad obfuscating change.
This also adds a leading space for unknown reasons
after the KERN_SOH <level>.
> > diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> > index ce277ee0a28a..14a7f023f20b 100644
> > --- a/drivers/char/Kconfig
> > +++ b/drivers/char/Kconfig
> > @@ -66,6 +66,14 @@ config TTY_PRINTK
> >
> > If unsure, say N.
> >
> > +config TTY_PRINTK_LEVEL
> > + depends on TTY_PRINTK
> > + int "ttyprintk log level (1-7)"
> > + range 1 7
> > + default "6"
> > + help
> > + Printk log level to use for ttyprintk messages.
> > +
> > config PRINTER
> > tristate "Parallel printer support"
> > depends on PARPORT
> > diff --git a/drivers/char/ttyprintk.c b/drivers/char/ttyprintk.c
> > index 67549ce88cc9..22fbd483b5dc 100644
> > --- a/drivers/char/ttyprintk.c
> > +++ b/drivers/char/ttyprintk.c
> > @@ -37,6 +37,8 @@ static struct ttyprintk_port tpk_port;
> > */
> > #define TPK_STR_SIZE 508 /* should be bigger then max expected line length */
> > #define TPK_MAX_ROOM 4096 /* we could assume 4K for instance */
> > +#define TPK_PREFIX KERN_SOH __stringify(CONFIG_TTY_PRINTK_LEVEL) " [U]"
I think this should be
#define TPK_PREFIX KERN_SOH __stringify(CONFIG_TTY_PRINTK_LEVEL)
> > +
> > static int tpk_curr;
> >
> > static char tpk_buffer[TPK_STR_SIZE + 4];
> > @@ -45,7 +47,7 @@ static void tpk_flush(void)
> > {
> > if (tpk_curr > 0) {
> > tpk_buffer[tpk_curr] = '\0';
> > - pr_info("[U] %s\n", tpk_buffer);
> > + printk(TPK_PREFIX " %s\n", tpk_buffer);
and this
printk(TPK_PREFIX "[U] %s\n", tpk_buffer);
> > tpk_curr = 0;
> > }
> > }
> > --
> > 2.11.0
> >
>
>
next prev parent reply other threads:[~2018-09-07 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 17:28 Peter Korsgaard
2018-09-07 7:50 ` Peter Korsgaard
2018-09-07 8:03 ` Joe Perches [this message]
2018-09-07 8:11 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc10850410b2c58c2bfbfa4f412403db7c82b535.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®