From: Guenter Roeck <linux@roeck-us.net>
To: cschneider@radiodata.biz
Cc: linux-hwmon@vger.kernel.org, Christian Schneider <christian@ch-sc.de>
Subject: Re: [PATCH] Fix sysfs_notify and kobject_uevent in fan_alarm_notify
Date: Mon, 17 Jun 2019 10:04:22 -0700 [thread overview]
Message-ID: <20190617170422.GA13276@roeck-us.net> (raw)
In-Reply-To: <20190617093343.1366-1-cschneider@radiodata.biz>
On Mon, Jun 17, 2019 at 11:33:43AM +0200, cschneider@radiodata.biz wrote:
> From: Christian Schneider <christian@ch-sc.de>
>
> sysfs_notify and kobject_uevent are passed the wrong kobject.
> that why notifications can't be received and uevents have the wrong path.
> this patch fixes this.
>
> Signed-off-by: Christian Schneider <cschneider@radiodata.biz>
Applied.
In the future, please version your patches, add a change log,
and reflect the subsystem and driver in the subject line.
Thanks,
Guenter
> ---
> drivers/hwmon/gpio-fan.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/hwmon/gpio-fan.c b/drivers/hwmon/gpio-fan.c
> index 84753680a4e8..76377791ff0e 100644
> --- a/drivers/hwmon/gpio-fan.c
> +++ b/drivers/hwmon/gpio-fan.c
> @@ -54,8 +54,8 @@ static void fan_alarm_notify(struct work_struct *ws)
> struct gpio_fan_data *fan_data =
> container_of(ws, struct gpio_fan_data, alarm_work);
>
> - sysfs_notify(&fan_data->dev->kobj, NULL, "fan1_alarm");
> - kobject_uevent(&fan_data->dev->kobj, KOBJ_CHANGE);
> + sysfs_notify(&fan_data->hwmon_dev->kobj, NULL, "fan1_alarm");
> + kobject_uevent(&fan_data->hwmon_dev->kobj, KOBJ_CHANGE);
> }
>
> static irqreturn_t fan_alarm_irq_handler(int irq, void *dev_id)
next prev parent reply other threads:[~2019-06-17 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 9:33 [PATCH] Fix sysfs_notify and kobject_uevent in fan_alarm_notify cschneider
2019-06-17 17:04 ` Guenter Roeck [this message]
2019-06-19 8:47 ` Christian Schneider
2019-06-19 10:00 ` Christian Schneider
2019-06-19 19:53 ` Guenter Roeck
2019-06-21 8:30 ` Christian Schneider
2019-06-21 14:05 ` Guenter Roeck
2019-06-19 19:55 ` Guenter Roeck
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=20190617170422.GA13276@roeck-us.net \
--to=linux@roeck-us.net \
--cc=christian@ch-sc.de \
--cc=cschneider@radiodata.biz \
--cc=linux-hwmon@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 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.