From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DEBUG_LL platform updates for 3.2
Date: Mon, 10 Oct 2011 14:32:46 +0100 [thread overview]
Message-ID: <20111010133246.GG2451@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <201110101320.24457.arnd@arndb.de>
On Mon, Oct 10, 2011 at 12:20:24PM +0100, Arnd Bergmann wrote:
> On Monday 10 October 2011, Will Deacon wrote:
> > Do you have any other ideas?
>
> I think the best solution would be to ask Russell to put all the dependencies
> into a non-rebasing branch and publish that, or to alternatively merge your
> patches through his tree instead, with my Ack.
I don't think asking Russell to maintain a stable branch for each series
scales very well if multiple people are doing cross-platform work at the
same time. If he's happy merging platform code via his tree, then I'd prefer
to go down that route. In this case, it might make sense to try and catch
conflicts between his tree and arm-soc before they hit Linus (I guess -next
will take care of this?).
> Both of these will also have to wait for a few more days until Russell
> is back online.
Ok, I wasn't aware that we was away.
> Can you check if the devel-stable branch in his tree already contains the
> dependencies?
I just had a quick look and I can't seem them outside of the unstable for-next
branch.
Cheers,
Will
next prev parent reply other threads:[~2011-10-10 13:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:38 [GIT PULL] DEBUG_LL platform updates for 3.2 Will Deacon
2011-10-03 8:35 ` Will Deacon
2011-10-07 20:51 ` Arnd Bergmann
2011-10-10 10:36 ` Will Deacon
2011-10-10 11:20 ` Arnd Bergmann
2011-10-10 13:32 ` Will Deacon [this message]
2011-10-11 7:52 ` Shawn Guo
2011-10-11 13:33 ` Arnd Bergmann
2011-10-11 15:09 ` Will Deacon
2011-10-11 18:48 ` Will Deacon
2011-10-11 19:25 ` Arnd Bergmann
2011-10-12 0:03 ` Nicolas Pitre
2011-10-12 8:30 ` Arnd Bergmann
2011-10-13 8:28 ` Russell King - ARM Linux
2011-10-13 13:39 ` Nicolas Pitre
2011-10-13 14:05 ` Russell King - ARM Linux
2011-10-13 18:36 ` Nicolas Pitre
2011-10-13 14:50 ` Arnd Bergmann
2011-10-13 23:09 ` Ryan Mallon
2011-10-13 23:40 ` Ryan Mallon
2011-10-14 2:32 ` Nicolas Pitre
2011-10-12 8:38 ` Jamie Iles
2011-10-12 20:16 ` Nicolas Pitre
2011-10-13 8:23 ` Russell King - ARM Linux
2011-10-13 18:46 ` Nicolas Pitre
2011-10-12 17:29 ` Russell King - ARM Linux
2011-10-12 17:35 ` Will Deacon
2011-10-12 18:01 ` Russell King - ARM Linux
2011-10-12 18:05 ` Will Deacon
2011-10-17 8:25 ` Russell King - ARM Linux
2011-10-17 9:23 ` Will Deacon
2011-10-20 14:57 ` Arnd Bergmann
2011-10-21 10:59 ` Will Deacon
2011-10-21 14:48 ` Rob Herring
2011-10-21 15:11 ` Arnd Bergmann
2011-10-21 15:15 ` Will Deacon
2011-10-21 18:03 ` Rob Herring
2011-10-21 23:04 ` Rob Herring
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=20111010133246.GG2451@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).