From: David Brownell <david-b@pacbell.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>,
Andrew Victor <linux@maxim.org.za>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Patrice Vilchez <patrice.vilchez@rfo.atmel.com>,
Richard Purdie <rpurdie@rpsys.net>,
linux-kernel@vger.kernel.org, kernel@avr32linux.org
Subject: Re: [PATCH -mm 2/2] PWM LED driver
Date: Mon, 28 Jan 2008 01:41:11 -0800 [thread overview]
Message-ID: <200801280141.12424.david-b@pacbell.net> (raw)
In-Reply-To: <20080128012932.bfbbd97d.akpm@linux-foundation.org>
On Monday 28 January 2008, Andrew Morton wrote:
> > - if (i > 0) {
> > - for (i = i - 1; i >= 0; i--) {
> > - led_classdev_unregister(&leds[i].cdev);
> > - pwm_channel_free(&leds[i].pwmc);
> > - }
> > + while (i-- > 0) {
> > + led_classdev_unregister(&leds[i].cdev);
> > + pwm_channel_free(&leds[i].pwmc);
> > }
>
> Looks OK, although I'd say that `while (--i >= 0)' is more idiomatic -
> predecrement, postincrement and all that?
Except for the "unsigned i;" declaration earlier... given that,
"while (true) cpu_relax();" becomes maximally idiomatic. :)
Odd how PDP-11 idioms linger. Just because C was designed on
that processor ...
next prev parent reply other threads:[~2008-01-28 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 14:33 [PATCH -mm 0/2] AVR32 PWM driver and example user Haavard Skinnemoen
2008-01-24 14:33 ` [PATCH -mm 1/2] Basic PWM driver for AVR32 and AT91 Haavard Skinnemoen
2008-01-24 14:33 ` [PATCH -mm 2/2] PWM LED driver Haavard Skinnemoen
2008-01-28 5:32 ` Andrew Morton
2008-01-28 9:15 ` Haavard Skinnemoen
2008-01-28 9:29 ` Andrew Morton
2008-01-28 9:32 ` Haavard Skinnemoen
2008-01-28 9:41 ` David Brownell [this message]
2008-01-24 20:53 ` [PATCH -mm 1/2] Basic PWM driver for AVR32 and AT91 David Brownell
2008-01-27 14:16 ` Haavard Skinnemoen
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=200801280141.12424.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=hskinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=patrice.vilchez@rfo.atmel.com \
--cc=rpurdie@rpsys.net \
/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.