public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Anirudh Ghayal <aghayal@codeaurora.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Richard Purdie <rpurdie@rpsys.net>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Trilok Soni <tsoni@codeaurora.org>
Subject: Re: [PATCH V1] led: pm8xxx: Add pm8xxx leds driver
Date: Wed, 29 Jun 2011 11:28:56 -0700	[thread overview]
Message-ID: <4E0B6EE8.9070202@codeaurora.org> (raw)
In-Reply-To: <1308739783-4643-1-git-send-email-aghayal@codeaurora.org>

On 06/22/2011 03:49 AM, Anirudh Ghayal wrote:
> +
> +/**
> + * struct pm8xxx_led_data - internal led data structure
> + * @led_classdev - led class device
> + * @id - led index
> + * @led_brightness - led brightness levels
> + * @work - workqueue for led
> + * @lock - to protect the transactions
> + * @reg - cached value of led register
> + */

This isn't kerneldoc notation.

> +fail_id_check:
> +	if (i > 0) {
> +		for (i = i - 1; i >= 0; i--) {
> +			int index = pdata->leds[i].flags;
> +			mutex_destroy(&led[index].lock);
> +			led_classdev_unregister(&led[index].cdev);
> +		}
> +	}

if (i > 0) is redundant here.

> +/**
> + * enum pm8xxx_leds - PMIC8XXX supported led ids
> + * @PM8XXX_ID_LED_KB_LIGHT - keyboard backlight led
> + * @PM8XXX_ID_LED_0 - First low current led
> + * @PM8XXX_ID_LED_1 - Second low current led
> + * @PM8XXX_ID_LED_2 - Third low current led
> + * @PM8XXX_ID_FLASH_LED_0 - First flash led
> + * @PM8XXX_ID_FLASH_LED_0 - Second flash led
> + */
> +

This isn't kerneldoc notation.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.


      reply	other threads:[~2011-06-29 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 10:49 [PATCH V1] led: pm8xxx: Add pm8xxx leds driver Anirudh Ghayal
2011-06-29 18:28 ` Stephen Boyd [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=4E0B6EE8.9070202@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=aghayal@codeaurora.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=tsoni@codeaurora.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox