[PATCH v6 0/2] Add device tree support for i.mx51/53 boards

Arnd Bergmann arnd at arndb.de
Tue Oct 18 09:39:22 EDT 2011


On Tuesday 18 October 2011, Russell King - ARM Linux wrote:
> 
> On Tue, Oct 18, 2011 at 12:18:46PM +0200, Sascha Hauer wrote:
> > 
> > On Mon, Oct 17, 2011 at 08:42:15AM +0800, Shawn Guo wrote:
> > > Changes since v5:
> > >  * Retrieve fixed clock frequency from device tree
> > > 
> > > Changes since v4:
> > >  * Rebase onto imx-features branch
> > >  * Have devices in soc dtsi as "disabled" and explicitly enable the
> > >    ones in board dts as "okay"
> > >  * Utilize of_irq_init() infrastructure added by Rob Herring recently
> > > 
> > > Shawn Guo (2):
> > >       arm/mx5: add device tree support for imx53 boards
> > >       arm/mx5: add device tree support for imx51 babbage
> > 
> > You sent this patches to Arnd but without saying what he should do with
> > them. Shall I queue them up or does Arnd handle them? Same with the
> > include cleanup series.
> 
> I think you should - the arm-soc tree is there to act as an integration
> tree for the various SoC maintainers.  Patches for SoCs where there's
> an active maintainer should still be handled by the SoC maintainer (and
> either applied to their git tree or forwarded upstream) unless there is
> agreement to do otherwise.

Yes, definitely. I don't mind getting occasional pull requests from
backup maintainers when the main person is not available or when there
is a distinct area being worked on by one particular person, but please
always communicate very clearly what is going on. The last thing I want
is overriding a maintainer or having to decide between two people
giving me conflicting messages over the same code.

Shawn, if you want me to apply patches, please be more specific in
the introductory mail with something like "As agreed with Sascha,
please merge these into the arm-soc tree", or put Sascha in the To
field and address him when the patches should go through the imx
tree. If you don't address either of us directly, the likely
outcome is that we will both ignore the series.

	Arnd



More information about the linux-arm-kernel mailing list