From: Petr Mladek <pmladek@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kieran Bingham <kbingham@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
John Ogness <john.ogness@linutronix.de>,
Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2][next] update gdb scripts for lockless printk ringbuffer
Date: Tue, 1 Sep 2020 14:31:13 +0200 [thread overview]
Message-ID: <20200901123113.GO4928@alley> (raw)
In-Reply-To: <20200825171756.830d5895eb40d2dded2803ae@linux-foundation.org>
On Tue 2020-08-25 17:17:56, Andrew Morton wrote:
> On Tue, 25 Aug 2020 14:35:42 +0200 Petr Mladek <pmladek@suse.com> wrote:
>
> > Andrew, would you mind when I take the three gdb/lockless-printk
> > related changes via printk tree to avoid synchronization problems?
>
> No probs. If such patches turn up in linux-next I just drop my copy.
> After checking that the patches fully match...
I have just pushed the two patches into printk/linux.git, branch
printk-rework.
Andrew's typo fix has been squashed into the 2nd patch.
Best Regards,
Petr
prev parent reply other threads:[~2020-09-01 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 21:25 [PATCH 0/2][next] update gdb scripts for lockless printk ringbuffer John Ogness
2020-08-14 21:25 ` [PATCH 1/2][next] scripts/gdb: add utils.read_ulong() John Ogness
2020-08-14 22:29 ` Nick Desaulniers
2020-08-14 21:25 ` [PATCH 2/2][next] scripts/gdb: update for lockless printk ringbuffer John Ogness
2020-08-14 22:24 ` [PATCH 0/2][next] update gdb scripts " Nick Desaulniers
2020-08-21 8:08 ` Petr Mladek
2020-08-21 8:55 ` Jan Kiszka
2020-08-24 9:20 ` Kieran Bingham
2020-08-25 12:35 ` Petr Mladek
2020-08-25 13:53 ` Jan Kiszka
2020-08-26 0:17 ` Andrew Morton
2020-09-01 12:31 ` 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=20200901123113.GO4928@alley \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=john.ogness@linutronix.de \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).