From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH RFC] kobject_uevent: notify uevent sysfs file on changes
Date: Thu, 16 May 2024 13:17:34 +0200 [thread overview]
Message-ID: <2024051640-earthen-granite-0847@gregkh> (raw)
In-Reply-To: <20240516-uevent-sysfs-notify-v1-1-2ebb39930c09@weissschuh.net>
On Thu, May 16, 2024 at 12:27:58PM +0200, Thomas Weißschuh wrote:
> The sysfs file "uevent" that exists for each device
> contains the same information that is attached to uevents emitted via
> netlink (or the usermode helper).
> This is useful for userspace which interacts with sysfs directly,
> without using (lib)udev.
>
> However it is not possible to actually get notified when the data in
> the "uevent" file changes.
What is wrong with listening to the uevent that is happening when the
file changes?
> Enable these notifications, so that the "uevent" file can be used
> together with inotify and friends.
uevent files are meant to be listened to by the uevent itself, why not do
that?
thanks,
greg k-h
next prev parent reply other threads:[~2024-05-16 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 10:27 [PATCH RFC] kobject_uevent: notify uevent sysfs file on changes Thomas Weißschuh
2024-05-16 11:17 ` Greg Kroah-Hartman [this message]
2024-05-16 17:41 ` Thomas Weißschuh
2024-05-16 18:28 ` Greg Kroah-Hartman
2024-05-16 18:32 ` Greg Kroah-Hartman
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=2024051640-earthen-granite-0847@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rafael@kernel.org \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).