All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Tom Zanussi <zanussi@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2] bootconfig: Only load bootconfig if "config=bootconfig" is on the kernel cmdline (was: bootconfig: Add "disable_bootconfig" cmdline option to disable bootconfig)
Date: Tue, 4 Feb 2020 15:43:00 +0000	[thread overview]
Message-ID: <CAHk-=wjTT81QUTAEbDPY=dJE2E18M_K2RhxSUxWmcbMyZUpm5w@mail.gmail.com> (raw)
In-Reply-To: <20200204093302.593cb82e@oasis.local.home>

On Tue, Feb 4, 2020 at 2:33 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> I wonder if we need the "config=" part. Would "bootconfig" be
> sufficient, or is it better to keep it for documentation purposes.

I suspect "bootconfig" is sufficient, if it's easier to parse.

            Linus

      reply	other threads:[~2020-02-04 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 10:31 [GIT PULL] tracing: Changes for 5.6 Steven Rostedt
2020-02-04 11:54 ` Linus Torvalds
2020-02-04 12:28   ` Steven Rostedt
2020-02-04 12:43     ` [PATCH] bootconfig: Add "disable_bootconfig" cmdline option to disable bootconfig Steven Rostedt
2020-02-04 13:19     ` [GIT PULL] tracing: Changes for 5.6 Linus Torvalds
2020-02-04 13:46       ` Steven Rostedt
2020-02-04 14:25         ` [PATCH v2] bootconfig: Only load bootconfig if "config=bootconfig" is on the kernel cmdline (was: bootconfig: Add "disable_bootconfig" cmdline option to disable bootconfig) Steven Rostedt
2020-02-04 14:33           ` Steven Rostedt
2020-02-04 15:43             ` Linus Torvalds [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='CAHk-=wjTT81QUTAEbDPY=dJE2E18M_K2RhxSUxWmcbMyZUpm5w@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=zanussi@kernel.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 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.