[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YzQQfW3h70OIiT14@linutronix.de>
Date: Wed, 28 Sep 2022 11:14:37 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: Ren Zhijie <renzhijie2@...wei.com>, akpm@...ux-foundation.org,
ndesaulniers@...gle.com, nathan@...nel.org, vbabka@...e.cz,
masahiroy@...nel.org, arnd@...db.de, seanjc@...gle.com,
hannes@...xchg.org, ojeda@...nel.org, mhiramat@...nel.org,
dmitry.torokhov@...il.com, atomlin@...hat.com, ddiss@...e.de,
christophe.leroy@...roup.eu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] init/Kconfig: fix unmet direct dependencies
On 2022-09-28 09:20:42 [+0200], Lukas Bulwahn wrote:
> > Couldn't this become a depends?
> It could also be a depends (to resolve the warning).
…
> It is just the question whether:
>
> When PROC_FS is not set, should the CHECKPOINT_RESTORE still be
> visible as a config option to add (and then automatically add
> PROC_FS)? Then select is right here.
then CHECKPOINT_RESTORE is the only option selecting PROC_FS while
everyone else depends on it _or_ avoids using it in the absence of
PROC_FS.
Sebastian
Powered by blists - more mailing lists