From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] arm-soc: lpc32xx: platform updates
Date: Mon, 12 Nov 2012 14:34:58 +0000 [thread overview]
Message-ID: <201211121434.58468.arnd@arndb.de> (raw)
In-Reply-To: <50A0D053.8020602@antcom.de>
On Monday 12 November 2012, Roland Stigge wrote:
> this is a follow-up update of the previous pull request, adding only one patch
> to the LPC32xx platform (Motor PWM clock by Alban Bedel).
>
> The following changes since commit 91deef8069e7ffafac4467200e1d37af1b2d7c56:
>
> ARM: LPC32xx: Cleanup irq.c (2012-11-07 13:30:50 +0100)
>
> are available in the git repository at:
>
> git://git.antcom.de/linux-2.6.git lpc32xx/core
>
Pulled into next/soc, thanks!
It would be nice if you could start using signed tag for pull requests
and put a little series description into that tag. Ideally signed with
a gpg key that is trusted by other kernel developers, but just having the
changelog is good as well.
Arnd
next prev parent reply other threads:[~2012-11-12 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 12:52 [GIT PULL] arm-soc: lpc32xx: platform updates Roland Stigge
2012-11-12 10:32 ` Roland Stigge
2012-11-12 14:34 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-01 19:22 Roland Stigge
2012-07-03 19:52 ` Arnd Bergmann
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=201211121434.58468.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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