From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] AT91/AVR32 some common macros
Date: Tue, 03 Nov 2009 19:11:14 +0100 [thread overview]
Message-ID: <4AF07242.3070803@atmel.com> (raw)
Hi Linus,
If it not bother you too much to pull such a tiny and
trivial piece of code, can you please pull:
git://github.com/at91linux/linux-2.6-at91.git for-linus
I directly sent this to you as it require two arch subsystems to
synchronize. As I have some .32 fixes that are waiting for those
lines to be merged to go upstream, I thought it was worth a try.
You can receive the following changes:
Nicolas Ferre (2):
avr32: add two new at91 to cpu.h definition
at91: at91sam9g45 family: identify several chip versions
arch/arm/mach-at91/include/mach/cpu.h | 9 +++++++++
arch/avr32/mach-at32ap/include/mach/cpu.h | 3 +++
2 files changed, 12 insertions(+), 0 deletions(-)
--
Nicolas Ferre
next reply other threads:[~2009-11-03 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 18:11 Nicolas Ferre [this message]
2009-11-03 18:15 ` [GIT PULL] AT91/AVR32 some common macros Linus Torvalds
2009-11-03 18:56 ` Matthew Palmer
2009-11-04 10:00 ` Nicolas Ferre
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=4AF07242.3070803@atmel.com \
--to=nicolas.ferre@atmel.com \
--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).