From: Valdis.Kletnieks@vt.edu
To: David Rientjes <rientjes@google.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Robin Holt <holt@sgi.com>, Ingo Molnar <mingo@elte.hu>,
Greg KH <gregkh@suse.de>, "David S. Miller" <davem@davemloft.net>,
Jens Axboe <axboe@kernel.dk>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/8] init: rename CONFIG_EMBEDDED to CONFIG_EXPERT
Date: Thu, 30 Dec 2010 16:56:05 -0500 [thread overview]
Message-ID: <15080.1293746165@localhost> (raw)
In-Reply-To: Your message of "Thu, 30 Dec 2010 11:17:32 PST." <alpine.DEB.2.00.1012301055340.12995@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Thu, 30 Dec 2010 11:17:32 PST, David Rientjes said:
> Instead of CONFIG_EXPERT select CONFIG_EMBEDDED, we could add a ninth
> patch which does CONFIG_EMBEDDED select CONFIG_EXPERT and tag it in some
> way so we know it's only temporary for the merge window to find new
> CONFIG_EMBEDDED entries.
What's the plan for those people who are currently on (say) 2.6.35, next
upgrade to 2.6.39 or .40, and thus miss the 9th temporary patch? They'll run
'make oldconfig' - if they get prompted, do we want to add a line to the help
text that says "This used to be called EMBEDDED"?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-12-30 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 4:02 [patch 1/8] init: rename CONFIG_EMBEDDED to CONFIG_EXPERT David Rientjes
2010-12-30 4:02 ` [patch 2/8] arch: " David Rientjes
2010-12-30 4:02 ` [patch 3/8] drivers: " David Rientjes
2010-12-30 4:02 ` [patch 4/8] fs: " David Rientjes
2010-12-30 4:02 ` [patch 5/8] block: " David Rientjes
2010-12-30 4:02 ` [patch 6/8] init: " David Rientjes
2010-12-30 4:02 ` [patch 7/8] lib: " David Rientjes
2010-12-30 4:02 ` [patch 8/8] usr: " David Rientjes
2010-12-30 9:04 ` [patch 1/8] init: " Ingo Molnar
2010-12-30 12:45 ` Robin Holt
2010-12-30 12:50 ` Arnd Bergmann
2010-12-30 13:10 ` Robin Holt
2010-12-30 19:17 ` David Rientjes
2010-12-30 21:56 ` Valdis.Kletnieks [this message]
2011-01-03 20:10 ` Andrew Morton
2011-01-03 21:56 ` David Rientjes
2011-01-02 10:29 ` David Woodhouse
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=15080.1293746165@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=holt@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.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