From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Kees Cook <keescook@chromium.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] enable early printing of hashed pointers
Date: Mon, 28 May 2018 09:59:15 -0400 [thread overview]
Message-ID: <20180528135915.GG4613@thunk.org> (raw)
In-Reply-To: <1527472002-11571-1-git-send-email-me@tobin.cc>
On Mon, May 28, 2018 at 11:46:38AM +1000, Tobin C. Harding wrote:
>
> During the versions of this set I have been totally confused about which
> patches go through which tree. This version again puts all 4 patches
> together in the hope they will go through Andrew's tree.
I'm also happy to take the whole patch series through the random tree
if everyone else is OK with it.
Thoughts?
- Ted
next prev parent reply other threads:[~2018-05-28 13:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 1:46 [PATCH v6 0/4] enable early printing of hashed pointers Tobin C. Harding
2018-05-28 1:46 ` [PATCH v6 1/4] random: Fix whitespace pre random-bytes work Tobin C. Harding
2018-05-28 1:46 ` [PATCH v6 2/4] random: Return nbytes filled from hw RNG Tobin C. Harding
2018-05-28 1:46 ` [PATCH v6 3/4] vsprintf: Use hw RNG for ptr_key Tobin C. Harding
2018-05-31 20:46 ` Steven Rostedt
2018-05-28 1:46 ` [PATCH v6 4/4] vsprintf: Add command line option debug_boot_weak_hash Tobin C. Harding
2018-05-28 17:40 ` Randy Dunlap
2018-05-30 4:27 ` Tobin C. Harding
2018-05-31 21:35 ` Steven Rostedt
2018-05-31 22:46 ` Tobin C. Harding
2018-05-28 13:59 ` Theodore Y. Ts'o [this message]
2018-06-06 23:31 ` [PATCH v6 0/4] enable early printing of hashed pointers Tobin C. Harding
2018-06-07 14:00 ` Theodore Y. Ts'o
2018-06-07 21:36 ` Tobin C. Harding
2018-05-31 18:52 ` Steven Rostedt
2018-06-05 14:21 ` Anna-Maria Gleixner
2018-06-06 13:08 ` Anna-Maria Gleixner
2018-06-06 23:29 ` Tobin C. Harding
2018-06-06 13:02 ` Thomas Gleixner
2018-06-06 23:30 ` Tobin C. Harding
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=20180528135915.GG4613@thunk.org \
--to=tytso@mit.edu \
--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=me@tobin.cc \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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