From: Nicholas Mc Guire <der.herr@hofr.at>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Linux Embedded Maillist <linux-embedded@vger.kernel.org>
Subject: Re: Renaming of CONFIG_EMBEDDED to CONFIG_EXPERT
Date: Sat, 1 Jan 2011 09:01:25 +0100 [thread overview]
Message-ID: <20110101080125.GA4040@opentech.at> (raw)
In-Reply-To: <AANLkTik90vOtkBKDiU5O_gtyWYHd-_VSeYCqRwn2Vcim@mail.gmail.com>
On Sat, 01 Jan 2011, Paul Gortmaker wrote:
> Given the high traffic on LKML, some folks probably haven't seen this
> thread, which proposes to rename the CONFIG_EMBEDDED option to
> CONFIG_EXPERT.
>
> https://patchwork.kernel.org/patch/438671/
>
what would be the advantage of such a change ? is there an intent to introduce
an actual CONFIG_EMBEDDED dedicated to embedded systems ?
The argument in the above patch that it requires experts to modify these
settings holds for a lot of items in the kernel config and if that is the
prime motivatino to flag these then an additional tag "EXPERT" along with
"NEW" and "EXPERIMENTAL" might make more sense (Aside from the help text
generally stating the sane-state any way with the common note that if you
don't knwo what you are doing say N...)
The main objection I would have is that it will break documentation (out of
tree docs that is) with little to no utility for the kernel developers.
hofrat
next prev parent reply other threads:[~2011-01-01 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 5:30 Renaming of CONFIG_EMBEDDED to CONFIG_EXPERT Paul Gortmaker
2011-01-01 8:01 ` Nicholas Mc Guire [this message]
2011-01-01 22:47 ` Paul Gortmaker
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=20110101080125.GA4040@opentech.at \
--to=der.herr@hofr.at \
--cc=linux-embedded@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).