From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Ren Zhijie <renzhijie2@huawei.com>,
akpm@linux-foundation.org, ndesaulniers@google.com,
nathan@kernel.org, vbabka@suse.cz, masahiroy@kernel.org,
arnd@arndb.de, seanjc@google.com, hannes@cmpxchg.org,
ojeda@kernel.org, mhiramat@kernel.org, dmitry.torokhov@gmail.com,
atomlin@redhat.com, ddiss@suse.de, christophe.leroy@csgroup.eu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] init/Kconfig: fix unmet direct dependencies
Date: Wed, 28 Sep 2022 11:14:37 +0200 [thread overview]
Message-ID: <YzQQfW3h70OIiT14@linutronix.de> (raw)
In-Reply-To: <CAKXUXMxGt9UGhw9Ap_M3U2AF1vw2dX7WpDO71=UwV0Be3t4sNw@mail.gmail.com>
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
next prev parent reply other threads:[~2022-09-28 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:49 Ren Zhijie
2022-09-28 7:01 ` Sebastian Andrzej Siewior
2022-09-28 7:20 ` Lukas Bulwahn
2022-09-28 7:52 ` Ren Zhijie
2022-09-28 9:14 ` Sebastian Andrzej Siewior [this message]
2022-09-28 9:32 ` Arnd Bergmann
2022-09-28 11:43 ` Lukas Bulwahn
2022-09-29 6:48 ` Ren Zhijie
2022-09-28 7:12 ` Lukas Bulwahn
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=YzQQfW3h70OIiT14@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ddiss@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=masahiroy@kernel.org \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=renzhijie2@huawei.com \
--cc=seanjc@google.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®