All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Missing CPU mapping updates
Date: Wed, 23 Nov 2011 21:15:23 +0000	[thread overview]
Message-ID: <201111232115.23950.arnd@arndb.de> (raw)
In-Reply-To: <20111121102906.GA2437@mudshark.cambridge.arm.com>

On Monday 21 November 2011, Will Deacon wrote:
> On Wed, Nov 16, 2011 at 11:36:36AM +0000, Will Deacon wrote:
> > Highbank and IMX6 were merged recently and therefore missed out on the
> > logical CPU mapping updates. I've fixed them up in the branch below - please
> > pull!
> 
> I'd like these to go in for 3.2, so please can you pull them into arm-soc?

Done now, sorry for the delay.

> Sorry to pester, but in Prague you said that's what you wanted us to do!

That is right, it was my fault for not realizing I wouldn't be able to
deal with this during UDS or my following vacation, and I also forgot
to talk to Olof about it.

	Arnd

      reply	other threads:[~2011-11-23 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 11:36 [GIT PULL] Missing CPU mapping updates Will Deacon
2011-11-21 10:29 ` Will Deacon
2011-11-23 21:15   ` Arnd Bergmann [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=201111232115.23950.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.