On Wed, Sep 08, 2010 at 02:16:34PM +0200, Uwe Kleine-König wrote: > Hello Russell, > > On Wed, Sep 08, 2010 at 12:56:10PM +0100, Russell King - ARM Linux wrote: > > On Wed, Sep 08, 2010 at 10:11:13AM +0100, Russell King - ARM Linux wrote: > > > On Fri, Sep 03, 2010 at 09:23:29PM +0200, Uwe Kleine-König wrote: > > > > Hello, > > > > > > > > On Fri, Sep 03, 2010 at 12:19:26PM -0700, Erik Gilling wrote: > > > > > On Fri, Sep 3, 2010 at 12:01 PM, Uwe Kleine-König > > > > > > (hmm, I thought that patches that touch common files like > > > > > > arch/arm/Kconfig should go via rmk?!) > > > > > > > > > > I looked and saw that others (specifically samsung) had submitted this > > > > > fix directly to Linus. I'm still learning the ropes here and am happy > > > > > to hear some clarification either way. > > > > > > > > Note that just me wondering if it's right doesn't necessarily means it's > > > > not. Russell, can you comment? Is it trivial enough and obviously only > > > > tegra related that it's OK? > > > > > > The problem happens when there's related changes already in others git > > > trees which clash or conflict with those changes. > > > > > > This whole CONFIG_ZRELADDR thing seems like a step backwards towards a > > > situation where we will get conflicts with multiple changes - but without > > > gaining anything substantial in moving away from Makefile.boot. > > > > > > Unless someone can come up with a real justification for CONFIG_ZRELADDR > > > I'm mindful to revert it. (But - if people have sent these changes to > > > Linus already, that's going to make reverting it a lot harder.) > > > > This is what I'm considering committing to sort out this ZRELADDR mess - > > it gives people who want AUTO_ZRELADDR their pie, while allowing us to > > keep the proven reliability of original method of handling ZRELADDR. > Would be OK for me. We might have to fix up some machines though. Any ideas what needs to be fixed? And is that an acked-by ? -- 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