From: Masami Hiramatsu <mhiramat@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: 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>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: linux-next: Tree for Feb 25 (BOOT_CONFIG)
Date: Tue, 25 Feb 2020 19:23:04 +0900 [thread overview]
Message-ID: <20200225192304.f3ccd36bd1c451e3a1969255@kernel.org> (raw)
In-Reply-To: <7e8f78b4-12f9-6bd3-72dc-08152fbe9345@infradead.org>
On Mon, 24 Feb 2020 22:58:01 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 2/24/20 7:24 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200224:
> >
>
>
> on i386:
>
> WARNING: unmet direct dependencies detected for BOOT_CONFIG
> Depends on [n]: BLK_DEV_INITRD [=n]
> Selected by [y]:
> - BOOTTIME_TRACING [=y] && TRACING_SUPPORT [=y] && FTRACE [=y] && TRACING [=y]
Oops, thanks for reporting!
So I made the Boottime tracing selects the bootconfig, but the bootconfig depends on initrd support.
Hmm, should I make BOOTTIME_TRACING depends on BLK_DEV_INITRD??
Thank you,
>
>
> Full randconfig file is attached.
>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-02-25 10:23 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 [this message]
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
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=20200225192304.f3ccd36bd1c451e3a1969255@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).