devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Olof Johansson <olof@lixom.net>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL v2] at91: irqdomain and device tree for 3.4
Date: Fri, 2 Mar 2012 13:27:23 +0000	[thread overview]
Message-ID: <201203021327.24417.arnd@arndb.de> (raw)
In-Reply-To: <4F4F8D66.7040205@atmel.com>

On Thursday 01 March 2012, Nicolas Ferre wrote:
> This pull request supersedes the previous:
> "[GIT PULL] at91: irqdomain and device tree for AIC and GPIO"
> 
> This series adds irqdomain and device tree support for both the
> interrupt and GPIO controllers of AT91 SoC. It has been discussed a lot
> and I think that I have addressed all comments and advices.
> 
> To the AIC, GPIO device tree work, it also adds the the conversion of the 
> PIT and TC timers, the PIO3 support and some basic LED and gpio-keys entries.
> 
> The irqdomain work takes advantage of Grant's patch series that is present
> in:
> git://git.secretlab.ca/git/linux-2.6 irqdomain/next
> This branch is merged into this tree, on top of at91/base2+cleanup (aka cleanup2)
> and before the application of new AT91 material.
> 
> 
> The following changes since commit 89d4a1753b6632327f18d6c8e0842b366b736621:
> 
>   Merge branch 'irqdomain/next' of git://git.secretlab.ca/git/linux-2.6 (2012-03-01 13:26:51 +0100)
 
Pulled into next/dt, looks good!

Thanks,

	Arnd

      reply	other threads:[~2012-03-02 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 14:53 [GIT PULL v2] at91: irqdomain and device tree for 3.4 Nicolas Ferre
2012-03-02 13:27 ` 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=201203021327.24417.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=olof@lixom.net \
    --cc=plagnioj@jcrosoft.com \
    /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).