linux-kernel - Re: Reasons for oldconfig resetting config options to =m

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] [day] [month] [year] [list]

Message-ID: <02e44659-230c-7774-9060-f6a9626edd1e@nh2.me>
Date:   Sun, 21 Apr 2019 18:47:40 +0200
From:   Niklas Hambüchen <mail@....me>
To:     Randy Dunlap <rdunlap@...radead.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: Reasons for oldconfig resetting config options to =m

On 2019-04-21 17:55, Randy Dunlap wrote:
> When using 'make menuconfig', enter /usb_storage and it says:
> ...
>   │   Depends on: USB_SUPPORT [=y] && USB [=m] && SCSI [=m]
> 
> HTH.  There is nothing quite as explicit as your example output.

Hmm OK.

The menuconfig approach is what I've used so far manually, but it does not work so well for batch / CI use.

Thanks nevertheless for the detail explanation!