From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Arnd Bergmann <arnd@arndb.de>, 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: Mon, 3 Jan 2011 12:10:30 -0800 [thread overview]
Message-ID: <20110103121030.921f6ff2.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1012301055340.12995@chino.kir.corp.google.com>
On Thu, 30 Dec 2010 11:17:32 -0800 (PST)
David Rientjes <rientjes@google.com> wrote:
> On Thu, 30 Dec 2010, Arnd Bergmann wrote:
>
> > > Doesn't this patch series break the 'bisectable' rule for patches?
> > > I think you can get by with adding a CONFIG_EXPERT selects CONFIG_EMBEDDED
> > > in the first patch and the last patch removing that same selects.
> >
> > How about leaving it that way during the merge window even? That would
> > help people sending git pull requests that add new dependencies on
> > CONFIG_EMBEDDED. David can submit another patch that removes the
> > temporary CONFIG_EMBEDDED option along with any new users in -rc2
> > or for 2.6.39 then.
> >
>
> Ok, so there are a few pending EMBEDDED dependency additions in linux-next
> as of next-20101230, which should be a pretty good indicator of what type
> of conflict we might risk during the merge window.
>
> - three new defconfig files:
>
> 89ba4d12: arch/arm/configs/ag5evm_defconfig
> 6cfce27c: arch/arm/configs/omap1_defconfig
> d58f0967: arch/blackfin/configs/BF561-EZKIT-SMP_defconfig
>
> - 3ce05168 (drm/kms: load fbcon from drm_kms_helper)
>
> - b595076a (tree-wide: fix comment/printk typos)
>
> 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.
>
> Andrew, this would be going through your -mm tree anyway, so how would you
> prefer to merge it?
um, one big patch shortly after -rc1 is released?
next prev parent reply other threads:[~2011-01-03 20:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 4:02 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
2011-01-03 20:10 ` Andrew Morton [this message]
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=20110103121030.921f6ff2.akpm@linux-foundation.org \
--to=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
Powered by JetHome