All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, kernel@avr32linux.org,
	patrice.vilchez@atmel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] avr32: add two new at91 to cpu.h definition
Date: Mon, 06 Jul 2009 11:39:41 +0200	[thread overview]
Message-ID: <4A51C65D.90304@atmel.com> (raw)
In-Reply-To: <20090706111954.723badb9@hskinnemoen-d830>

Haavard Skinnemoen :
> Nicolas Ferre wrote:
>> Somme common drivers will need those at91 cpu_is_xxx() definitions. As
>> at91sam9g10 and at91sam9g45 are on the way to linus' tree, here is the patch
>> that adds those chips to cpu.h in AVR32 architecture.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> 
> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
> 
>> ---
>> Inclusion in linux-2.6-arm.git/devel:
>>
>> at91sam9g10: b784b7c03723891876c9053c589150a4062f9455
>> at91sam9g45: fddcc0ae58edefeb7ac1e460411d7dfbe8ebdacc
> 
> Do you want me to take this patch, or is it better if it goes in along
> the rest through the ARM tree?

You can take this patch as it will still go in linux-next.

I try to collect all patches that are related to those products
introduction in linux-next (for 2.6.32).

Thanks Haavard. Bye,
-- 
Nicolas Ferre


      reply	other threads:[~2009-07-06  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 10:15 [PATCH] avr32: add two new at91 to cpu.h definition Nicolas Ferre
2009-07-06  9:19 ` Haavard Skinnemoen
2009-07-06  9:39   ` 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=4A51C65D.90304@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=kernel@avr32linux.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrice.vilchez@atmel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.