Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1486326
| From | Joe Perches <joe@perches.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] leds: triggers: Check return value of kobject_uevent_env() |
| Date | 2016-09-19 12:20 +0200 |
| Message-ID | <sj3Q5-498-19@gated-at.bofh.it> (permalink) |
| References | <sj3Gq-43G-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 2016-09-19 at 12:05 +0200, Jacek Anaszewski wrote:
> Log error message if kobject_uevent_env() fails in led_trigger_set().
trivia:
> diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
[]
> @@ -141,7 +141,9 @@ void led_trigger_set(struct led_classdev *led_cdev, struct led_trigger *trig)
> if (event) {
> envp[0] = event;
> envp[1] = NULL;
> - kobject_uevent_env(&led_cdev->dev->kobj, KOBJ_CHANGE, envp);
> + if (kobject_uevent_env(&led_cdev->dev->kobj, KOBJ_CHANGE, envp))
> + dev_err(led_cdev->dev,
> + "led_trigger_set: Error sending uevent\n");
It is generally better to use %s, __func__ than to embed
a function name in the format string.
+ dev_err(led_cdev->dev, "%s: Error sending uevent\n",
+ __func__);
Then Function renaming and code refactoring is less
error prone.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v2] leds: triggers: Check return value of kobject_uevent_env() Jacek Anaszewski <j.anaszewski@samsung.com> - 2016-09-19 12:10 +0200 Re: [PATCH v2] leds: triggers: Check return value of kobject_uevent_env() Joe Perches <joe@perches.com> - 2016-09-19 12:20 +0200
csiph-web