linux-kernel - Re: linux-next: Tree for Feb 25 (BOOT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200225192304.f3ccd36bd1c451e3a1969255@kernel.org>
Date:   Tue, 25 Feb 2020 19:23:04 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     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>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: linux-next: Tree for Feb 25 (BOOT_CONFIG)

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??

Thank you,

> 
> 
> Full randconfig file is attached.
> 
> -- 
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@...radead.org>


-- 
Masami Hiramatsu <mhiramat@...nel.org>