From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()
Date: Tue, 30 Aug 2016 10:07:03 +0900 [thread overview]
Message-ID: <20160830010703.GA2200@swordfish> (raw)
In-Reply-To: <20160829151600.GM4866@pathway.suse.cz>
On (08/29/16 17:16), Petr Mladek wrote:
[..]
> The comment above is not longer valid.
oh, yes. it shouldn't even be there.
> > -static void print_nmi_seq_line(struct nmi_seq_buf *s, int start, int end)
> > +static void __print_nmi_seq_line(const char *text, int len)
>
> Also the name of the function might be confusing because it is not
> longer used only for the seq buffer. I would rename it to
> something like:
>
> printk_nmi_flush_line()
sounds good.
> > +static void print_nmi_seq_line(struct nmi_seq_buf *s, int start, int end)
> > +{
>
> Then I would rename also this function to something like:
>
> printk_nmi_flush_seq_line()
sounds good.
> > + const char *buf = s->buffer + start;
> > +
> > + __print_nmi_seq_line(buf, (end - start) + 1);
> > +}
> > +
>
> Othrewise, it looks fine. With the above suggested changes, feel
> free to add:
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
thanks, will re-spin today.
-ss
next prev parent reply other threads:[~2016-08-30 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 12:32 [PATCH] printk/nmi: avoid direct printk()-s from __printk_nmi_flush() Sergey Senozhatsky
2016-08-29 15:16 ` Petr Mladek
2016-08-30 1:07 ` Sergey Senozhatsky [this message]
2016-08-30 7:58 ` Sergey Senozhatsky
2016-08-30 9:04 ` Petr Mladek
2016-08-30 9:39 ` Sergey Senozhatsky
2016-08-30 11:19 ` Petr Mladek
2016-08-31 4:00 ` Sergey Senozhatsky
2016-09-01 7:55 ` Sergey Senozhatsky
2016-09-01 8:17 ` Petr Mladek
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=20160830010703.GA2200@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.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