[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200225220551.d9a409bc04b77cdf48eae3ea@kernel.org>
Date: Tue, 25 Feb 2020 22:05:51 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: linux-next: Tree for Feb 25 (BOOT_CONFIG)
On Tue, 25 Feb 2020 19:23:04 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:
> On Mon, 24 Feb 2020 22:58:01 -0800
> Randy Dunlap <rdunlap@...radead.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??
OK, there are 3 options.
1) make BOOTTIME_TRACING depends on BOOT_CONFIG
2) make BOOTTIME_TRACING selects BLK_DEV_INITRD
3) make BOOT_CONFIG selects BLK_DEV_INITRD (and BOOTTIME_TRACING=n by default)
Or, I'll hurry to implement CONFIG_BUILTIN_BOOT_CONFIG support.
Thank you,
>
> Thank you,
>
> >
> >
> > Full randconfig file is attached.
> >
> > --
> > ~Randy
> > Reported-by: Randy Dunlap <rdunlap@...radead.org>
>
>
> --
> Masami Hiramatsu <mhiramat@...nel.org>
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists