From: Steven Rostedt <rostedt@goodmis.org>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Theodore Ts'o <tytso@mit.edu>, Petr Mladek <pmladek@suse.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] fix: enable early printing of hashed pointers
Date: Mon, 9 Jul 2018 22:07:16 -0400 [thread overview]
Message-ID: <20180709220716.16f4f288@vmware.local.home> (raw)
In-Reply-To: <20180710002519.5044-1-me@tobin.cc>
On Tue, 10 Jul 2018 10:25:16 +1000
"Tobin C. Harding" <me@tobin.cc> wrote:
> Since I'm a massive noob I did not realise that since v7 of this set was
> applied to random-next already that doing incremental versions was
> pointless.
I wouldn't say you are a noob anymore. You are making the same types of
mistakes that seasoned kernel developers make ;-)
-- Steve
next prev parent reply other threads:[~2018-07-10 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 0:25 [PATCH 0/3] fix: enable early printing of hashed pointers Tobin C. Harding
2018-07-10 0:25 ` [PATCH 1/3] random: Remove unnecessary cast Tobin C. Harding
2018-07-10 2:06 ` Steven Rostedt
2018-07-10 0:25 ` [PATCH 2/3] vsprintf: Remove incorrect EXPORT_SYMBOL Tobin C. Harding
2018-07-10 2:12 ` Steven Rostedt
2018-07-10 0:25 ` [PATCH 3/3] docs: Fix docs for boot parameter debug_boot_weak_hash Tobin C. Harding
2018-07-10 2:14 ` Steven Rostedt
2018-07-10 2:07 ` Steven Rostedt [this message]
2018-07-10 2:59 ` [PATCH 0/3] fix: enable early printing of hashed pointers 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=20180709220716.16f4f288@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=sergey.senozhatsky@gmail.com \
--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