From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Padmanabha Srinivasaiah <treasure4paddy@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: tracing : bootconfig : Early boot config for non intrd systems
Date: Sun, 13 Mar 2022 16:48:57 +0900 [thread overview]
Message-ID: <20220313164857.cdd7aa7d7977bfff6c91fdff@kernel.org> (raw)
In-Reply-To: <20220312101606.41a9fc64@rorschach.local.home>
On Sat, 12 Mar 2022 10:16:06 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 12 Mar 2022 10:15:24 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Sat, 12 Mar 2022 15:53:58 +0900
> > Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > > OK, please try below patch. You can embed your bootconfig in the kernel via
> > > CONFIG_EMBED_BOOT_CONFIG_FILE.
> > >
> > >
> > > >From 7478a8fbfe4669ee61fcb12b85b36d7e36f992ba Mon Sep 17 00:00:00 2001
> > > From: Masami Hiramatsu <mhiramat@kernel.org>
> > > Date: Sat, 12 Mar 2022 14:59:30 +0900
> > > Subject: [PATCH] bootconfig: Support embedding a bootconfig file in kernel
> >
> > I'm going to try this out, because there was a few times I could have
> > used this.
> >
>
> Oh, and can you send this as a separate patch so that it triggers my
> scripts?
OK, let me clean it up and add a document how to use it.
Thank you,
>
> Thanks,
>
> -- Steve
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-03-13 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 18:40 Padmanabha Srinivasaiah
2022-03-08 7:36 ` Masami Hiramatsu
2022-03-08 17:48 ` Padmanabha Srinivasaiah
2022-03-09 8:01 ` Masami Hiramatsu
2022-03-09 19:06 ` Padmanabha Srinivasaiah
2022-03-12 6:53 ` Masami Hiramatsu
2022-03-12 15:15 ` Steven Rostedt
2022-03-12 15:16 ` Steven Rostedt
2022-03-13 7:48 ` Masami Hiramatsu [this message]
2022-03-13 9:40 ` Masami Hiramatsu
2022-03-16 14:06 ` Padmanabha Srinivasaiah
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=20220313164857.cdd7aa7d7977bfff6c91fdff@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=treasure4paddy@gmail.com \
/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
all inboxes | Powered by JetHome®