From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
voice <voice.shen@atmel.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] at91: one fix for 3.6
Date: Tue, 18 Sep 2012 10:30:55 +0200 [thread overview]
Message-ID: <5058313F.8060704@atmel.com> (raw)
Arnd, Olof,
We have one last minute fix. It can help us to use the device tree for
GPIO interrupt attached devices. I have based my tag on top of the "fixes" pull
request that I've already sent to you.
I hope that it could make it for 3.6-final.
The following changes since commit 51a6149b89b822cacf572b2ca2a15cb6f2232b11:
ARM: at91/feature-removal-schedule: delay at91_mci removal (2012-08-27 09:59:36 +0200)
are available in the git repository at:
git://github.com/at91linux/linux-at91.git tags/at91-fixes
for you to fetch changes up to 51ac51a6a5ab5f0aff46c4757ba4c32f3f8f7a2e:
ARM: at91: fix missing #interrupt-cells on gpio-controller (2012-09-17 10:25:01 +0200)
----------------------------------------------------------------
Modify AT91 device tree files for making the GPIO interrupts work.
----------------------------------------------------------------
Jean-Christophe PLAGNIOL-VILLARD (1):
ARM: at91: fix missing #interrupt-cells on gpio-controller
arch/arm/boot/dts/at91sam9260.dtsi | 3 +++
arch/arm/boot/dts/at91sam9263.dtsi | 5 +++++
arch/arm/boot/dts/at91sam9g45.dtsi | 5 +++++
arch/arm/boot/dts/at91sam9n12.dtsi | 4 ++++
arch/arm/boot/dts/at91sam9x5.dtsi | 4 ++++
5 files changed, 21 insertions(+)
Thanks, best regards,
--
Nicolas Ferre
next reply other threads:[~2012-09-18 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:30 Nicolas Ferre [this message]
2012-09-18 14:44 ` [GIT PULL] at91: one fix for 3.6 Olof Johansson
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=5058313F.8060704@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
--cc=voice.shen@atmel.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