Am Dienstag, 28. Mai 2013, 15:30:29 schrieb Stephen Warren: > On 05/28/2013 11:26 AM, Stephen Warren wrote: > > From: Stephen Warren <swarren@xxxxxxxxxx> > > > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
