public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 cleanups for v4.2
Date: Wed, 20 May 2015 17:40:12 +0200	[thread overview]
Message-ID: <2271356.zMzJ8CSdNi@wuerfel> (raw)
In-Reply-To: <CACRpkdbRXN4bBWdqpMVRJ6bqqKrkO-8ssfWmHfbguNjjbjGpGw@mail.gmail.com>

On Monday 18 May 2015 15:23:49 Linus Walleij wrote:
> Hi ARM SoC people,
> 
> this is a pull request for some additional cleanups requested by Arnd
> in this message:
> http://marc.info/?l=linux-arm-kernel&m=143151859309482&w=2
> 
> Please pull this into next/cleanup where the dependent patch is.
> A patch from the next/dt, commit 487934109d33e1749d3034899685111bca6ffd0b
> "ARM: ux500: add SCU and WD to device tree" is needed for this to
> work but since I regard all DT work as essentially orthogonal I rely on
> the two to merge up in the end and work nicely.
> 
> Please pull this into next/cleanup!
> 

Pulled into next/cleanup, thanks!

	Arnd

      reply	other threads:[~2015-05-20 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 13:23 [GIT PULL] ux500 cleanups for v4.2 Linus Walleij
2015-05-20 15:40 ` 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=2271356.zMzJ8CSdNi@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