From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Pierre Kuo <vichy.kuo@gmail.com>
Cc: pmladek@suse.com, sergey.senozhatsky@gmail.com,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
joe@perches.com
Subject: Re: [PATCH] printk: Modify operators of printed_len
Date: Sat, 8 Jul 2017 14:12:51 +0900 [thread overview]
Message-ID: <20170708051251.GB488@tigerII.localdomain> (raw)
In-Reply-To: <1499482273-10638-1-git-send-email-vichy.kuo@gmail.com>
On (07/08/17 10:51), Pierre Kuo wrote:
> In 8b1742c9c207, we remove printk-recursion detection code in
> vprintk_emit(), where it is the first place that printed_len calculated.
> After removing above detection, it seems we can directly assign the
> result of log_output to printed_len.
>
> Signed-off-by: Pierre Kuo <vichy.kuo@gmail.com>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
> ---
> kernel/printk/printk.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index fc47863..a2a8cac 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -1701,7 +1701,7 @@ asmlinkage int vprintk_emit(int facility, int level,
> size_t text_len = 0;
> enum log_flags lflags = 0;
> unsigned long flags;
> - int printed_len = 0;
> + int printed_len;
> bool in_sched = false;
>
> if (level == LOGLEVEL_SCHED) {
> @@ -1754,7 +1754,7 @@ asmlinkage int vprintk_emit(int facility, int level,
> if (dict)
> lflags |= LOG_PREFIX|LOG_NEWLINE;
>
> - printed_len += log_output(facility, level, lflags, dict, dictlen, text, text_len);
> + printed_len = log_output(facility, level, lflags, dict, dictlen, text, text_len);
>
> logbuf_unlock_irqrestore(flags);
>
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2017-07-08 5:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 2:51 Pierre Kuo
2017-07-08 5:12 ` Sergey Senozhatsky [this message]
2017-07-10 13:51 ` Petr Mladek
2017-07-11 4:00 ` pierre kuo
-- strict thread matches above, loose matches on Subject: below --
2017-07-07 16:30 Pierre Kuo
2017-07-07 17:12 ` Joe Perches
2017-07-07 20:32 ` pierre kuo
2017-07-07 23:03 ` Joe Perches
2017-07-08 2:49 ` pierre kuo
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=20170708051251.GB488@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=vichy.kuo@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
all inboxes | Powered by JetHome®