From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Rob Landley <rob@landley.net>, linux-kernel@vger.kernel.org
Subject: Re: Why is CONFIG_VT forced on?
Date: Mon, 30 Dec 2019 21:33:14 -0500 [thread overview]
Message-ID: <20191231023314.GC3669@mit.edu> (raw)
In-Reply-To: <8059d1c4-759d-9911-73c7-211f8576e7f2@infradead.org>
On Mon, Dec 30, 2019 at 06:03:26PM -0800, Randy Dunlap wrote:
> >
> > So if I disable CONFIG_EXPERT, using miniconfig I then need to manually switch on:
> >
> > ./init/Kconfig: bool "Namespaces support" if EXPERT
> >
> > So nobody noticed you have a structural "this config option actually switches
> > this thing _off_" implemented via magic symbol then?
Perhaps because the right thing happens if you enable CONFIG_EXPERT
using "make menuconfig"? It also looks like the right thing happens
if you edit the .config and then run "make oldconfig".
Personally, I never use miniconfig, so it's not anything *I* ever
noticed in all of my years of kernel development. Usually, the way
that I manage configs is "make menuconfig", or editing the .config
directly, or "make savedefconfig" / "make olddefconfig".
Cheers,
- Ted
next prev parent reply other threads:[~2019-12-31 2:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 0:30 Why is CONFIG_VT forced on? Rob Landley
2019-12-31 0:36 ` Randy Dunlap
2019-12-31 0:53 ` Rob Landley
2019-12-31 0:59 ` Randy Dunlap
2019-12-31 1:45 ` Rob Landley
2019-12-31 2:00 ` Randy Dunlap
2019-12-31 2:04 ` Rob Landley
2019-12-31 2:03 ` Randy Dunlap
2019-12-31 2:33 ` Theodore Y. Ts'o [this message]
2019-12-31 2:40 ` Al Viro
2019-12-31 2:52 ` Al Viro
2019-12-31 3:27 ` Rob Landley
2019-12-31 3:53 ` Al Viro
2019-12-31 4:18 ` Al Viro
2019-12-31 5:58 ` Al Viro
2020-01-01 20:41 ` [PATCH] menuconfig: restore prompt dependencies in help text Arvind Sankar
2020-01-01 21:04 ` Al Viro
2020-01-01 22:26 ` Arvind Sankar
2020-01-02 16:14 ` Randy Dunlap
2020-01-02 23:14 ` [PATCH] kconfig: " Arvind Sankar
2020-01-03 2:10 ` Masahiro Yamada
2020-01-03 4:20 ` Arvind Sankar
2019-12-31 1:55 ` Why is CONFIG_VT forced on? Theodore Y. Ts'o
2020-01-04 20:27 ` Enrico Weigelt, metux IT consult
2019-12-31 2:28 ` Al Viro
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=20191231023314.GC3669@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.