linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: at91sam9g10 chip identification changed
Date: Wed, 14 Apr 2010 17:40:34 +0200	[thread overview]
Message-ID: <4BC5E1F2.1000003@atmel.com> (raw)
In-Reply-To: <t2rcd73a99e1004140801ybff81f03x5c7fae2ace55afd6@mail.gmail.com>

Le 14/04/2010 17:01, Andrew Victor :
> hi Nicolas,
> 
>> I do not think it is a good idea:
> 
> Ok.  Then we'll go with your original patch.
> 
>  Acked-by: Andrew Victor <linux@maxim.org.za>

Queued in patch tracking system as 6056/1:

http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6056/1

Thanks, bye,
-- 
Nicolas Ferre

      reply	other threads:[~2010-04-14 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01  9:48 [PATCH] AT91: at91sam9g10 chip identification changed Nicolas Ferre
2010-04-12 18:44 ` Russell King - ARM Linux
2010-04-13  7:42 ` Andrew Victor
2010-04-14  8:14   ` Nicolas Ferre
2010-04-14 15:01     ` Andrew Victor
2010-04-14 15:40       ` 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=4BC5E1F2.1000003@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).