From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: avictor.za@gmail.com, linux-arm-kernel@lists.infradead.org
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AT91: add new at91 chips in at91sam9g45 family
Date: Fri, 11 Jun 2010 12:50:32 +0200 [thread overview]
Message-ID: <4C1214F8.80005@atmel.com> (raw)
In-Reply-To: <1273509900-30278-1-git-send-email-nicolas.ferre@atmel.com>
Le 10/05/2010 18:45, Nicolas Ferre :
> This is the basic support for at91sam9g46, at91sam9m10 and at91sam9m11. Those
> are just very basic cpu macros and clock definition.
>
> Signed-off-by: Patrice Vilchez <patrice.vilchez@atmel.com>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Acked-by Andrew Victor added.
Submitted as patch 6169/1
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6169/1
Best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2010-06-11 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 16:45 [PATCH] AT91: add new at91 chips in at91sam9g45 family Nicolas Ferre
2010-06-11 10:50 ` Nicolas Ferre [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=4C1214F8.80005@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=avictor.za@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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