Re: [PATCH] avr32: add some more at91 to cpu.h definition

[Nicolas Ferre]

Le 06/05/2011 14:04, Hans-Christian Egtvedt :
> On Fri, 2011-05-06 at 13:08 +0200, Nicolas Ferre wrote:
>> Somme common drivers will need those at91 cpu_is_xxx() definitions.
>> Those definitions are already in Linus' tree so if we want to use them
>> in common drivers, we will need them in AVR32 cpu.h file.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@xxxxxxxxx>
> 
> Will you push this update for 2.6.39? I don't have anything for Linus
> right now.

Ah, Linus has just pulled from our tree...
Maybe we can wait a few days to see if some fixes have to be pushed
upstream before -final...

> Acked-by: Hans-Christian Egtvedt <hans-christian.egtvedt@xxxxxxxxx>
> with one comment...

;-)

>> ---
>>  arch/avr32/mach-at32ap/include/mach/cpu.h |   13 +++++++++++++
>>  1 files changed, 13 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/avr32/mach-at32ap/include/mach/cpu.h b/arch/avr32/mach-at32ap/include/mach/cpu.h
>> index 9c96a13..a927d9e 100644
>> --- a/arch/avr32/mach-at32ap/include/mach/cpu.h
>> +++ b/arch/avr32/mach-at32ap/include/mach/cpu.h
>> @@ -31,8 +31,21 @@
>>  #define cpu_is_at91sam9263()	(0)
>>  #define cpu_is_at91sam9rl()	(0)
>>  #define cpu_is_at91cap9()	(0)
>> +#define cpu_is_at91cap9_revB()	(0)
>> +#define cpu_is_at91cap9_revC()	(0)
>>  #define cpu_is_at91sam9g10()	(0)
>> +#define cpu_is_at91sam9g20()	(0)
>>  #define cpu_is_at91sam9g45()	(0)
>>  #define cpu_is_at91sam9g45es()	(0)
>> +#define cpu_is_at91sam9m10()	(0)
>> +#define cpu_is_at91sam9g46()	(0)
>> +#define cpu_is_at91sam9m11()	(0)
>> +#define cpu_is_at91sam9x5()	(0)
>> +#define cpu_is_at91sam9g15()	(0)
>> +#define cpu_is_at91sam9g35()	(0)
>> +#define cpu_is_at91sam9x35()	(0)
>> +#define cpu_is_at91sam9g25()	(0)
>> +#define cpu_is_at91sam9x25()	(0)
>> +
> 
> No need for this extra newline.

True.

>>  #endif /* __ASM_ARCH_CPU_H */

Bye,
-- 
Nicolas Ferre

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/