From: gshark <gshark.jeong@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'Richard Purdie'" <rpurdie@rpsys.net>,
"'Daniel Jeong'" <daniel.jeong@gmail.com>
Subject: Re: [PATCH] backlight: lm3630: remove ret = -EIO of lm3630_backlight_register()
Date: Mon, 18 Feb 2013 10:48:55 +0900 [thread overview]
Message-ID: <51218897.2150420a.5715.ffff85d5@mx.google.com> (raw)
In-Reply-To: <00b801ce026c$8a90ec00$9fb2c400$%han@samsung.com>
2013년 02월 04일 09:14, Jingoo Han 쓴 글:
> There is no need to return -EIO, because backlight_device_register()
> already returns correct error values.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/video/backlight/lm3630_bl.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/video/backlight/lm3630_bl.c b/drivers/video/backlight/lm3630_bl.c
> index a6d637b..76a62e9 100644
> --- a/drivers/video/backlight/lm3630_bl.c
> +++ b/drivers/video/backlight/lm3630_bl.c
> @@ -320,7 +320,7 @@ static int lm3630_backlight_register(struct lm3630_chip_data *pchip,
> backlight_device_register(name, pchip->dev, pchip,
> &lm3630_bank_a_ops, &props);
> if (IS_ERR(pchip->bled1))
> - return -EIO;
> + return PTR_ERR(pchip->bled1);
> break;
> case BLED_2:
> props.brightness = pdata->init_brt_led2;
> @@ -329,7 +329,7 @@ static int lm3630_backlight_register(struct lm3630_chip_data *pchip,
> backlight_device_register(name, pchip->dev, pchip,
> &lm3630_bank_b_ops, &props);
> if (IS_ERR(pchip->bled2))
> - return -EIO;
> + return PTR_ERR(pchip->bled2);
> break;
> }
> return 0;
Thank you. This patch looks good for us.
Acked-by: Daniel Jeong<daniel.jeong@ti.com>
prev parent reply other threads:[~2013-02-18 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 0:14 Jingoo Han
2013-02-18 1:48 ` gshark [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=51218897.2150420a.5715.ffff85d5@mx.google.com \
--to=gshark.jeong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.jeong@gmail.com \
--cc=jg1.han@samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®