From: "Tobin C. Harding" <me@tobin.cc>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Theodore Ts'o <tytso@mit.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vsprintf: Add command line option debug_boot_weak_hash
Date: Thu, 17 May 2018 08:26:28 +1000 [thread overview]
Message-ID: <20180516222628.GC25268@eros> (raw)
In-Reply-To: <f9bacaa1-7741-d28e-29d1-4b42ae0c986f@infradead.org>
On Tue, May 15, 2018 at 08:29:47AM -0700, Randy Dunlap wrote:
> On 05/14/2018 09:38 PM, Tobin C. Harding wrote:
>
> > Documentation/admin-guide/kernel-parameters.txt | 8 ++++++++
> > lib/vsprintf.c | 18 ++++++++++++++++++
> > 2 files changed, 26 insertions(+)
> >
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index 3b8032431585..c95dd6704592 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -748,6 +748,14 @@
> >
> > debug [KNL] Enable kernel debugging (events log level).
> >
> > + debug_boot_weak_hash
> > + [KNL] Enable debugging early in the boot sequence. If
>
> That makes it sound like "debug_boot_weak_hash" turns on early debugging.
Thanks Randy, I'll have another go at writing this.
Tobin
prev parent reply other threads:[~2018-05-16 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 4:38 [PATCH] vsprintf: Add command line option debug_boot_weak_hash Tobin C. Harding
2018-05-15 14:33 ` Steven Rostedt
2018-05-15 15:29 ` Randy Dunlap
2018-05-16 22:26 ` Tobin C. Harding [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=20180516222628.GC25268@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.