All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: avictor.za@gmail.com, linux-arm-kernel@lists.arm.linux.org.uk,
	patrice.vilchez@atmel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] at91: Support for at91sam9g45: clocks management
Date: Thu, 04 Jun 2009 10:46:10 +0200	[thread overview]
Message-ID: <4A2789D2.2000001@atmel.com> (raw)
In-Reply-To: <20090604083332.GA3331@fluff.org.uk>

Ben Dooks :
> On Thu, Jun 04, 2009 at 10:48:01AM +0200, Nicolas Ferre wrote:
>> Add the at91sam9g45 series support to the AT91 generic clock file.
>> This takes care of the particularities of the PMC for this series.
>> It also takes advantage of the management by functionalities of
>> those PLLs and clocks.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> 
> personally, please don't post between open and subscriber only lists,
> this should really only be sent to linux-arm-kernel.

Ah ? Reading SubmittingPatches document, I see in section 6:
"Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org"

Is posting in "open" and "subscriber only" lists is a reason?


>> ---
>>  arch/arm/mach-at91/clock.c |   62 ++++++++++++++++++++++++++++++++++++-------
>>  1 files changed, 52 insertions(+), 10 deletions(-)
>>
>> diff --git a/arch/arm/mach-at91/clock.c b/arch/arm/mach-at91/clock.c
>> index bac578f..6396680 100644
>> --- a/arch/arm/mach-at91/clock.c
>> +++ b/arch/arm/mach-at91/clock.c
>> @@ -47,20 +47,25 @@
>>   * Chips have some kind of clocks : group them by functionality
>>   */
>>  #define cpu_has_utmi()		(  cpu_is_at91cap9() \
> 
> how does this pass checkpatch? no spaces after (.

Well, true, it does not. But, have a look at the result, it is so
prettier with those spaces: cpu_is_ directives are aligned.

It's a matter of taste and I considered breaking the rule here was not
so serious...

Thanks Ben.

Regards,
-- 
Nicolas Ferre


  reply	other threads:[~2009-06-04  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  8:48 [PATCH 1/3] at91: Basic support for at91sam9g45 series: header files Nicolas Ferre
2009-06-04  8:48 ` Nicolas Ferre
2009-06-23 14:24   ` Nicolas Ferre
2009-06-04  8:48 ` [PATCH 2/3] at91: Support for at91sam9g45: clocks management Nicolas Ferre
2009-06-04  8:33   ` Ben Dooks
2009-06-04  8:46     ` Nicolas Ferre [this message]
2009-06-04  8:48   ` Nicolas Ferre
2009-06-04  8:32     ` Nicolas Ferre
2009-06-04  8:48 ` [PATCH 3/3] at91: Support for at91sam9g45 series: core chip & board support Nicolas Ferre
2009-06-04  8:48   ` 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=4A2789D2.2000001@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=avictor.za@gmail.com \
    --cc=ben-linux@fluff.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.