From: Constantin Baranov <const@const.mimas.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, rpurdie@rpsys.net
Subject: Re: [PATCH 2.6.27-rc3] led: driver for LEDs on PCEngines ALIX.2 and ALIX.3 boards
Date: Sat, 23 Aug 2008 22:11:56 +0500 [thread overview]
Message-ID: <48B044DC.5040700@const.mimas.ru> (raw)
In-Reply-To: <20080822143143.4202f940.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 23 Aug 2008 02:08:15 +0500
> Constantin Baranov <const@const.mimas.ru> wrote:
>
>>> static int alix_led_resume(struct platform_device *dev)
>>> {
>>> int i;
>>> +
>>> for (i = 0; i < ARRAY_SIZE(alix_leds); i++)
>>> led_classdev_resume(&alix_leds[i].cdev);
>>> return 0;
>>> @@ -92,7 +95,7 @@ static int __init alix_led_probe(struct
>>> ret = led_classdev_register(&pdev->dev, &alix_leds[i].cdev);
>>>
>>> if (ret < 0) {
>>> - for (i = i - 2; i >= 0; i--)
>>> + while (--i >= 0)
>>> led_classdev_unregister(&alix_leds[i].cdev);
>>> }
>> At the first iteration this while-loop will attempt to unregister
>> device that has failed and thus is not registered.
>> My for-loop starts from device immediately before failed one.
>
> ug, OK, the complex expression in that for-loop is to blame.
>
> For maintinability we should aim for code which is as simple and as
> straightfroward as possible and which adheres to oft-used and
> well-understood kernel idioms.
>
> For example, this?
>
> static int __init alix_led_probe(struct platform_device *pdev)
> {
> int i;
> int ret;
>
> for (i = 0; i < ARRAY_SIZE(alix_leds); i++) {
> ret = led_classdev_register(&pdev->dev, &alix_leds[i].cdev);
> if (ret < 0)
> goto fail;
> }
> return 0;
>
> fail:
> while (--i >= 0)
> led_classdev_unregister(&alix_leds[i].cdev);
> return ret;
> }
>
> (note there's no longer a need for a fake initalisation of `ret')
>
>> Note that probe routine originates from leds-ams-delta.c.
>
> That's what you get for copying stuff :(
Well, this variant looks better and correct and still works.
Should I post again patch or fix-patch?
next prev parent reply other threads:[~2008-08-23 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 17:23 [PATCH 2.6.27-rc3] led: driver for LEDs on PCEngines ALIX.2 and ALIX.3 boards Constantin Baranov
2008-08-22 18:51 ` Andrew Morton
2008-08-22 19:44 ` Willy Tarreau
2008-08-22 21:08 ` Constantin Baranov
2008-08-22 21:31 ` Andrew Morton
2008-08-23 17:11 ` Constantin Baranov [this message]
2008-08-24 5:36 ` Andrew Morton
2008-08-24 10:08 ` Stefan Richter
2008-08-24 10:33 ` Stefan Richter
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=48B044DC.5040700@const.mimas.ru \
--to=const@const.mimas.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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.