From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Dietrich Subject: Re: [PATCH] ARM: tegra: rebuild tegra_defconfig Date: Wed, 29 May 2013 15:38:40 +0200 Message-ID: <2234363.J239kID5LN@fb07-iapwap2.physik.uni-giessen.de> References: <1369761972-31986-1-git-send-email-swarren@wwwdotorg.org> <51A521F5.2010206@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <51A521F5.2010206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephen Warren Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Stephen Warren List-Id: linux-tegra@vger.kernel.org Am Dienstag, 28. Mai 2013, 15:30:29 schrieb Stephen Warren: > On 05/28/2013 11:26 AM, Stephen Warren wrote: > > From: Stephen Warren > > > > This simply rebuilds tegra_defconfig on top of next-20130520. As such, it > > should introduce no changes; simply moving entries around due to Kconfig > > ordering changes. The apparent exceptions are: > > > > AUTO_ZRELADDR: Selected by ARM multi-platform support. > > MTD_CHAR: Removed in Kconfig. > > > > This should make it easier to create future defconfig patches on top of > > linux-next, since all the extraneous diffs have been removed. It also > > makes it more likely that once 3.12 comes around, this defconfig will > > already match what's required there. > > I've applied this (squashed it into) Tegra's for-3.11/defconfig branch. wouldn't it make more sense to apply such a patch just before the merge window closes (or better after some release candidate)? This way we would have a better chance to have a zero diff between defconfig and tegra_defconfig, e.g. not like 3.10 is now. Marc From mboxrd@z Thu Jan 1 00:00:00 1970 From: marvin24@gmx.de (Marc Dietrich) Date: Wed, 29 May 2013 15:38:40 +0200 Subject: [PATCH] ARM: tegra: rebuild tegra_defconfig In-Reply-To: <51A521F5.2010206@wwwdotorg.org> References: <1369761972-31986-1-git-send-email-swarren@wwwdotorg.org> <51A521F5.2010206@wwwdotorg.org> Message-ID: <2234363.J239kID5LN@fb07-iapwap2.physik.uni-giessen.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am Dienstag, 28. Mai 2013, 15:30:29 schrieb Stephen Warren: > On 05/28/2013 11:26 AM, Stephen Warren wrote: > > From: Stephen Warren > > > > This simply rebuilds tegra_defconfig on top of next-20130520. As such, it > > should introduce no changes; simply moving entries around due to Kconfig > > ordering changes. The apparent exceptions are: > > > > AUTO_ZRELADDR: Selected by ARM multi-platform support. > > MTD_CHAR: Removed in Kconfig. > > > > This should make it easier to create future defconfig patches on top of > > linux-next, since all the extraneous diffs have been removed. It also > > makes it more likely that once 3.12 comes around, this defconfig will > > already match what's required there. > > I've applied this (squashed it into) Tegra's for-3.11/defconfig branch. wouldn't it make more sense to apply such a patch just before the merge window closes (or better after some release candidate)? This way we would have a better chance to have a zero diff between defconfig and tegra_defconfig, e.g. not like 3.10 is now. Marc