From: Petr Mladek <pmladek@suse.com>
To: Pierre Kuo <vichy.kuo@gmail.com>
Cc: sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH v2] printk: Modify operators of printed_len and text_len
Date: Tue, 11 Jul 2017 10:30:47 +0200 [thread overview]
Message-ID: <20170711083047.GO23069@pathway.suse.cz> (raw)
In-Reply-To: <1499755255-6258-1-git-send-email-vichy.kuo@gmail.com>
On Tue 2017-07-11 14:40:55, Pierre Kuo wrote:
> With commit <ddb9baa82226> ("printk: report lost messages in printk
> safe/nmi contexts") and commit <8b1742c9c207> ("printk: remove zap_locks()
> function"), it seems we can remove initialization, "=0", of text_len and
> directly assign result of log_output to printed_len.
Just one small thing. The <> brackets should not be there around
the sha1 commit id. Otherwise, the patch looks fine to me.
Acked-by: Petr Mladek <pmladek@suse.com>
You do not need to resend the patch. I'll remove the brackets
when applying the patch. I'll wait few more days just in case
anyone has more comments on this patch.
Best Regards,
Petr
prev parent reply other threads:[~2017-07-11 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 6:40 Pierre Kuo
2017-07-11 8:30 ` Petr Mladek [this message]
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=20170711083047.GO23069@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--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
Powered by JetHome