From: Steven Rostedt <rostedt@goodmis•org>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Masami Hiramatsu <mhiramat@kernel•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH] bootconfig: Fix CONFIG_BOOTTIME_TRACING dependency issue
Date: Tue, 25 Feb 2020 12:53:35 -0500 [thread overview]
Message-ID: <20200225125335.5bbc3ed4@gandalf.local.home> (raw)
In-Reply-To: <c9604764-bd0f-67e9-56c8-fb6ffaf9b430@infradead.org>
On Tue, 25 Feb 2020 09:49:25 -0800
Randy Dunlap <rdunlap@infradead•org> wrote:
> > Fixes: d8a953ddde5e ("bootconfig: Set CONFIG_BOOT_CONFIG=n by default")
> > Reported-by: Randy Dunlap <rdunlap@infradead•org>
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel•org>
>
> Hi,
> I'm no fan of "select", but this does fix the kconfig warnings and
> build errors that I have reported. Thanks.
I'm not big on select either, but this is fine (I'm running it through my
tests now).
>
> Acked-by: Randy Dunlap <rdunlap@infradead•org> # build-tested
Is it OK if I change this to "Tested-by:"?
-- Steve
next prev parent reply other threads:[~2020-02-25 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 3:24 linux-next: Tree for Feb 25 Stephen Rothwell
2020-02-25 6:58 ` linux-next: Tree for Feb 25 (BOOT_CONFIG) Randy Dunlap
2020-02-25 10:23 ` Masami Hiramatsu
2020-02-25 13:05 ` Masami Hiramatsu
2020-02-25 14:36 ` [PATCH] bootconfig: Fix CONFIG_BOOTTIME_TRACING dependency issue Masami Hiramatsu
2020-02-25 17:49 ` Randy Dunlap
2020-02-25 17:53 ` Steven Rostedt [this message]
2020-02-25 17:59 ` Randy Dunlap
2020-02-26 1:34 ` Masami Hiramatsu
2020-02-27 9:18 ` Geert Uytterhoeven
2020-02-27 13:22 ` Masami Hiramatsu
2020-02-27 14:25 ` Steven Rostedt
2020-02-27 14:33 ` Geert Uytterhoeven
2020-02-27 16:38 ` Masami Hiramatsu
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=20200225125335.5bbc3ed4@gandalf.local.home \
--to=rostedt@goodmis$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@kernel$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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