public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Patch Merging Path - RMK or Arnd?
Date: Sun, 21 Aug 2011 13:49:36 +0100	[thread overview]
Message-ID: <20110821124936.GE28546@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110821112940.GB22917@e102144-lin.cambridge.arm.com>

On Sun, Aug 21, 2011 at 12:29:40PM +0100, Will Deacon wrote:
> Thinking about this a bit more, (4) can also avoid the situation where one
> tree pulls the series but the other tree has reservations about the code and
> decides not to take the patches. So, in my case, I could get the core
> changes merged by Russell and then send you the full set afterwards.

I think (4) is the sensible one too.

      reply	other threads:[~2011-08-21 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 12:49 Patch Merging Path - RMK or Arnd? Will Deacon
2011-08-19 14:21 ` Arnd Bergmann
2011-08-19 14:45   ` Will Deacon
2011-08-20 21:23     ` Arnd Bergmann
2011-08-21 11:29       ` Will Deacon
2011-08-21 12:49         ` Russell King - ARM Linux [this message]

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=20110821124936.GE28546@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox