mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 王洪辉 <honghui.wang@ucas.com.cn>
To: "Petr Mladek" <pmladek@suse.com>
Cc: "Sergey Senozhatsky" <senozhatsky@chromium.org>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"John Ogness" <john.ogness@linutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] printk: fix a typo of comment
Date: Wed, 23 Nov 2022 17:21:05 +0800	[thread overview]
Message-ID: <tencent_58021F77224429481C4676D4@qq.com> (raw)
In-Reply-To: <Y3yvmMq8FsK85qjl@alley>

Thanks,Best Regards!Wang Honghui&nbsp;&nbsp;------------------&nbsp;Original&nbsp;------------------From: &nbsp;"Petr&nbsp;Mladek"<pmladek@suse.com>;Date: &nbsp;Tue, Nov 22, 2022 07:16 PMTo: &nbsp;"Wang Honghui"<honghui.wang@ucas.com.cn>; Cc: &nbsp;"Sergey Senozhatsky"<senozhatsky@chromium.org>; "Steven Rostedt"<rostedt@goodmis.org>; "John Ogness"<john.ogness@linutronix.de>; "linux-kernel"<linux-kernel@vger.kernel.org>; Subject: &nbsp;Re: [PATCH V2] printk: fix a typo of comment&nbsp;On Tue 2022-11-22 16:50:36, Wang Honghui wrote:&gt; Fix a typo of comment&gt; &gt; Signed-off-by: Wang Honghui <honghui.wang@ucas.com.cn>JFYI, the patch has been committed into printk/linux.git, branch for-6.2.Best Regards,PetrPS: I have added John's Reviewed-by from v1 [1]. This version of the patch just fixed the typo that John mentioned there[1] https://lore.kernel.org/r/874jurqt5g.fsf@jogness.linutronix.de</honghui.wang@ucas.com.cn></linux-kernel@vger.kernel.org></john.ogness@linutronix.de></rostedt@goodmis.org></senozhatsky@chromium.org></honghui.wang@ucas.com.cn></pmladek@suse.com>

      reply	other threads:[~2022-11-23  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  8:50 Wang Honghui
2022-11-22 11:16 ` Petr Mladek
2022-11-23  9:21   ` 王洪辉 [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=tencent_58021F77224429481C4676D4@qq.com \
    --to=honghui.wang@ucas.com.cn \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    /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®