From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>, linux-input@vger.kernel.org
Subject: Re: [PATCH] hid: thingm: remove not needed error message
Date: Mon, 25 Apr 2016 09:35:37 +0200 [thread overview]
Message-ID: <20160425073537.GB23234@mail.corp.redhat.com> (raw)
In-Reply-To: <5717CB61.3080603@gmail.com>
On Apr 20 2016 or thereabouts, Heiner Kallweit wrote:
> LED core takes care of handling failed calls to thingm_let_set.
> - print error message in set_brightness_delayed or
> - pass error to caller in led_set_brightness_sync
> Also the error message here doesn't provide any hint what actually
> went wrong. Therefore remove it.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Works for me:
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@rehat.com>
> ---
> drivers/hid/hid-thingm.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/hid/hid-thingm.c b/drivers/hid/hid-thingm.c
> index 2507bbe..9ad9c6e 100644
> --- a/drivers/hid/hid-thingm.c
> +++ b/drivers/hid/hid-thingm.c
> @@ -148,13 +148,8 @@ static int thingm_led_set(struct led_classdev *ldev,
> enum led_brightness brightness)
> {
> struct thingm_led *led = container_of(ldev, struct thingm_led, ldev);
> - int ret;
> -
> - ret = thingm_write_color(led->rgb);
> - if (ret)
> - hid_err(led->rgb->tdev->hdev, "failed to write color\n");
>
> - return ret;
> + return thingm_write_color(led->rgb);
> }
>
> static int thingm_init_led(struct thingm_led *led, const char *color_name,
> --
> 2.8.0
>
next prev parent reply other threads:[~2016-04-25 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 18:33 [PATCH] hid: thingm: remove not needed error message Heiner Kallweit
2016-04-25 7:35 ` Benjamin Tissoires [this message]
2016-04-25 9:31 ` Jiri Kosina
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=20160425073537.GB23234@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=hkallweit1@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.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