From: "Tobin C. Harding" <me@tobin.cc>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Kees Cook <keescook@chromium.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] enable early printing of hashed pointers
Date: Thu, 17 May 2018 08:41:58 +1000 [thread overview]
Message-ID: <20180516224158.GD25268@eros> (raw)
In-Reply-To: <20180516111348.1abf69a1@gandalf.local.home>
On Wed, May 16, 2018 at 11:13:48AM -0400, Steven Rostedt wrote:
>
> I think the series looks good, although if Linus takes my last patch,
> it may conflict badly with the third patch. I'll have to look into that.
I applied your PR patch ontop of mainline (imitating Linus pulling) any
yes patch 3 of this set has a merge conflict.
> Anyway, Andrew, you want to take this in your tree?
I split this set up into it's current form because Ted offered to take
it through his tree. There has been no response from him though since
doing so. He has ack'ed the first 2 patches (that touch
drivers/char/random.c and include/linux/random.c).
Since this is not overly urgent stuff is it easier for everyone involved
if I wait until the PR to Linus goes through then rebase this, add the
other vsprintf patch back onto the set and send it all to Andrew?
Usual disclaimer about being a massive noob, please correct me if I am
out of line. My aim is to make the job of others more simple.
thanks,
Tobin.
next prev parent reply other threads:[~2018-05-16 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 23:17 [PATCH v5 0/3] enable early printing of hashed pointers Tobin C. Harding
2018-05-15 23:17 ` [PATCH v5 1/3] random: Fix whitespace pre random-bytes work Tobin C. Harding
2018-05-15 23:17 ` [PATCH v5 2/3] random: Return nbytes filled from hw RNG Tobin C. Harding
2018-05-15 23:17 ` [PATCH v5 3/3] vsprintf: Use hw RNG for ptr_key Tobin C. Harding
2018-05-16 15:13 ` [PATCH v5 0/3] enable early printing of hashed pointers Steven Rostedt
2018-05-16 22:41 ` Tobin C. Harding [this message]
2018-05-22 15:33 ` Steven Rostedt
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=20180516224158.GD25268@eros \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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