All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
	keescook@chromium.org, anton@enomsg.org, ccross@android.com,
	tony.luck@intel.com, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org
Subject: Re: [PATCH] kernel/printk.c: Fixed mundane typos
Date: Tue, 30 Mar 2021 16:32:35 +0200	[thread overview]
Message-ID: <YGM2g4A1cnYZG8Bv@alley> (raw)
In-Reply-To: <87mtuk4xb3.fsf@jogness.linutronix.de>

On Tue 2021-03-30 14:53:52, John Ogness wrote:
> On 2021-03-30, Petr Mladek <pmladek@suse.com> wrote:
> > On Sun 2021-03-28 10:09:32, Bhaskar Chowdhury wrote:
> >> 
> >> s/sempahore/semaphore/
> >> s/exacly/exactly/
> >> s/unregistred/unregistered/
> >> s/interation/iteration/
> >> 
> >> 
> >> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> >
> > Reviewed-by: Petr Mladek <pmladek@suse.com>
> >
> > John,
> >
> > it conflicts with the patchset removing printk safe buffers[1].
> > Would you prefer to queue this into the patchset?
> > Or should I push it into printk/linux.git, printk-rework and you would
> > base v2 on top of it?
> 
> Go ahead and push it to printk-rework. I'll base v2 on top of it.

The patch is committed in printk/linux.git, branch printk-rework.
It is queued for 5.13.

Best Regards,
Petr

      reply	other threads:[~2021-03-30 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  4:39 [PATCH] kernel/printk.c: Fixed mundane typos Bhaskar Chowdhury
2021-03-30 12:51 ` Petr Mladek
2021-03-30 12:53   ` John Ogness
2021-03-30 14:32     ` 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=YGM2g4A1cnYZG8Bv@alley \
    --to=pmladek@suse.com \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=john.ogness@linutronix.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tony.luck@intel.com \
    --cc=unixbhaskar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.