From: Greg KH <gregkh@linuxfoundation.org>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: Colin Cross <ccross@android.com>,
linux-kernel@vger.kernel.org,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Richard Purdie <rpurdie@rpsys.net>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: triggers: send uevent when changing triggers
Date: Thu, 26 Jul 2012 09:51:12 -0700 [thread overview]
Message-ID: <20120726165112.GA23857@kroah.com> (raw)
In-Reply-To: <CAK5ve-LbNeJngQPE=893-ChJXEWJHg9km1Ev6GZYx4=Zrrxg9g@mail.gmail.com>
On Thu, Jul 26, 2012 at 01:03:11PM +0800, Bryan Wu wrote:
> Just one quick patch for my idea: emitting a uevent in sysfs_create_file().
>
> --
> diff --git a/fs/sysfs/file.c b/fs/sysfs/file.c
> index 00012e3..04da869 100644
> --- a/fs/sysfs/file.c
> +++ b/fs/sysfs/file.c
> @@ -570,10 +570,14 @@ int sysfs_add_file(struct sysfs_dirent *dir_sd,
> const struct attribute *attr,
>
> int sysfs_create_file(struct kobject * kobj, const struct attribute * attr)
> {
> + int err = 0;
> +
> BUG_ON(!kobj || !kobj->sd || !attr);
>
> - return sysfs_add_file(kobj->sd, attr, SYSFS_KOBJ_ATTR);
> + err = sysfs_add_file(kobj->sd, attr, SYSFS_KOBJ_ATTR);
> + kobject_uevent(kobj, KOBJ_CHANGE);
That's a veritable flood of change events when a new kobject is created,
right? It also created uevents for a device that has not told userspace
that it is even present, which could cause massive confusion, don't you
think?
greg k-h
next prev parent reply other threads:[~2012-07-26 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 0:32 [PATCH] leds: triggers: send uevent when changing triggers Colin Cross
2012-07-25 6:11 ` Bryan Wu
2012-07-25 14:36 ` Greg KH
2012-07-25 18:54 ` Colin Cross
2012-07-26 3:29 ` Bryan Wu
2012-07-26 3:59 ` Greg KH
2012-07-26 5:03 ` Bryan Wu
2012-07-26 16:51 ` Greg KH [this message]
2012-07-27 4:04 ` Bryan Wu
2012-07-31 18:28 ` Colin Cross
2012-08-07 2:57 ` Bryan Wu
2012-08-07 3:34 ` Greg KH
[not found] ` <CAK5ve-KLdwEqW6MLbusMRkaHBQkxTqOGLoVWzSmiuo2qxwtwmA@mail.gmail.com>
2012-08-07 3:43 ` Greg KH
2012-08-07 14:36 ` Henrique de Moraes Holschuh
2012-08-07 19:44 ` Colin Cross
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=20120726165112.GA23857@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bryan.wu@canonical.com \
--cc=ccross@android.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@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 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.