From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: LPC32xx: Device tree updates
Date: Wed, 10 Sep 2014 15:58:15 +0200 [thread overview]
Message-ID: <541058F7.8060809@antcom.de> (raw)
The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
are available in the git repository at:
git://git.antcom.de/linux-2.6 lpc32xx/dt
for you to fetch changes up to 280f965674dbc5090147724d90b701f2b81f07e3:
ARM: LPC32xx: Use DMA for both SSP channels (2014-09-10 15:41:30 +0200)
----------------------------------------------------------------
Roland Stigge (1):
ARM: LPC32xx: Use DMA for both SSP channels
arch/arm/boot/dts/lpc32xx.dtsi | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
next reply other threads:[~2014-09-10 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 13:58 Roland Stigge [this message]
2014-09-10 16:37 ` [GIT PULL] ARM: LPC32xx: Device tree updates Arnd Bergmann
2014-09-11 13:10 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2014-09-09 14:51 Roland Stigge
2014-09-09 15:43 ` Arnd Bergmann
2014-09-10 13:51 ` Roland Stigge
2014-09-10 14:26 ` Arnd Bergmann
2014-09-12 8:03 ` Linus Walleij
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=541058F7.8060809@antcom.de \
--to=stigge@antcom.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;
as well as URLs for NNTP newsgroup(s).