Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 fixes for the v3.8 series
Date: Mon, 28 Jan 2013 14:06:58 -0800	[thread overview]
Message-ID: <20130128220658.GC7789@quad.lixom.net> (raw)
In-Reply-To: <CACRpkdYhVbu2S6iD=SRnU1gMRNfau25ihOqoDoXvCrH71seREQ@mail.gmail.com>

On Fri, Jan 25, 2013 at 01:40:34PM +0100, Linus Walleij wrote:
> Hi ARM SoC guys,
> 
> here are three fixes for the Ux500 that need to go to the -rc:s.
> 
> Please pull them in!
> 
> Yours,
> Linus Walleij
> 
> 
> The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
> 
>   Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)
> 
> are available in the git repository at:
> 
>   http://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-stericsson.git
> tags/ux500-fixes-for-v3.8


Pulled, thanks.

Nit below:

> Steve Zhan (1):
>       ARM: ux500: add spin_unlock(&master_lock).

That's not a great patch subject, but I'm not going to ask a respin just for
it.


-Olof

      reply	other threads:[~2013-01-28 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 12:40 [GIT PULL] ux500 fixes for the v3.8 series Linus Walleij
2013-01-28 22:06 ` Olof Johansson [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=20130128220658.GC7789@quad.lixom.net \
    --to=olof@lixom.net \
    --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