From: Steven Rostedt <rostedt@goodmis.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
kernel test robot <lkp@intel.com>,
linux-sparse@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kbuild-all@lists.01.org
Subject: Re: [PATCH] printk: Make linux/printk.h self-contained
Date: Mon, 15 Jun 2020 15:17:27 -0400 [thread overview]
Message-ID: <20200615151727.3c7e9786@oasis.local.home> (raw)
In-Reply-To: <20200615114038.GA20708@gondor.apana.org.au>
On Mon, 15 Jun 2020 21:40:38 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Thanks for investigating. I now realise that this was sent against
> my first patch which did have this problem, which was fixed in my
> second patch. Sorry for the false alarm.
Which is why it is recommended that new patches start their own threads ;-)
That said,
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
for the v2 patch.
-- Steve
prev parent reply other threads:[~2020-06-15 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 12:51 [PATCH] printk: Make linux/printk.h self-contained Herbert Xu
2020-06-11 15:53 ` kernel test robot
2020-06-11 16:31 ` kernel test robot
2020-06-12 4:36 ` [v2 PATCH] " Herbert Xu
2020-06-12 9:49 ` Andy Shevchenko
2020-06-12 11:32 ` Sergey Senozhatsky
2020-06-12 13:14 ` Petr Mladek
2020-06-12 16:52 ` Peter Zijlstra
2020-06-13 12:28 ` [PATCH] " kernel test robot
2020-06-13 13:09 ` Herbert Xu
2020-06-13 14:29 ` Luc Van Oostenryck
2020-06-15 11:40 ` Herbert Xu
2020-06-15 19:17 ` Steven Rostedt [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=20200615151727.3c7e9786@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@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;
as well as URLs for NNTP newsgroup(s).