All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/2] Add device tree support for i.mx51/53 boards
Date: Tue, 18 Oct 2011 15:39:22 +0200	[thread overview]
Message-ID: <201110181539.22384.arnd@arndb.de> (raw)
In-Reply-To: <20111018102531.GN21648@n2100.arm.linux.org.uk>

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

  parent reply	other threads:[~2011-10-18 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17  0:42 [PATCH v6 0/2] Add device tree support for i.mx51/53 boards Shawn Guo
2011-10-17  0:42 ` [PATCH v6 1/2] arm/mx5: add device tree support for imx53 boards Shawn Guo
2011-10-17  0:42 ` [PATCH v6 2/2] arm/mx5: add device tree support for imx51 babbage Shawn Guo
2011-10-18 10:18 ` [PATCH v6 0/2] Add device tree support for i.mx51/53 boards Sascha Hauer
2011-10-18 10:25   ` Russell King - ARM Linux
2011-10-18 11:37     ` Shawn Guo
2011-10-18 13:39     ` Arnd Bergmann [this message]
2011-10-18 11:32   ` Shawn Guo
2011-10-25  1:21     ` Shawn Guo

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=201110181539.22384.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.