From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DEBUG_LL platform updates for 3.2
Date: Tue, 11 Oct 2011 21:25:19 +0200 [thread overview]
Message-ID: <2414781.rlNqTThJUN@wuerfel> (raw)
In-Reply-To: <20111011184821.GA11839@mudshark.cambridge.arm.com>
On Tuesday 11 October 2011 19:48:21 Will Deacon wrote:
> On Tue, Oct 11, 2011 at 04:09:15PM +0100, Will Deacon wrote:
> > For the cpu-mapping, I depend on:
> >
> > ARM: 7011/1: Add ARM cpu topology definition
> > ARM: 7060/1: smp: populate logical CPU mapping during boot
> > ARM: 7061/1: gic: convert logical CPU numbers into physical numbers
> >
> > which I can only see in Russell's for-next branch.
> >
> > For the debug-ll stuff, I depend on:
> >
> > ARM: 7072/1: debug: use kconfig choice for selecting DEBUG_LL UART
> >
> > and conflict with:
> >
> > ARM: 7097/1: debug: Move DEBUG_ICEDCC into the DEBUG_LL choice
> > ARM: 7096/1: debug: Add UART1 config choices
> > ARM: 7116/1: debug: provide dummy default option for DEBUG_LL UART choice
> > ARM: 7073/1: debug: augment DEBUG_LL Kconfig help to clarify behaviour
>
> I've stuck a debug-ll branch and a cpu-mapping branch here:
>
> git://github.com/wdeacon/linux-wd.git
Ok, thanks.
> (I finally gave up with my old broken git server!)
>
> These branches are based against -rc9 and I've cherry-picked the
> dependencies from Russell's for-next branch. I'm not sure that's good for
> anything, but it at least helps to show what's already in Russell's tree
> and what's currently outstanding.
I've stuck them into the arm-soc tree for now, so we get linux-next
coverage, but I won't send them to Linus this way because then we
would get the same commits twice in the history.
Russell, would be mind putting the 8 patches that Will listed above
into the devel-stable or some other non-rebasing branch so we can
rebase Will's patches on top of that?
Alternatively, if you prefer you could also throw them out of your
tree so I can send them to Linus, or you could pull the two patch
series from Will into your arm tree so I can drop them completely.
Arnnd
next prev parent reply other threads:[~2011-10-11 19:25 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
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 [this message]
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=2414781.rlNqTThJUN@wuerfel \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox