From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 1/2] driver core: class: expose the class kobject
Date: Tue, 15 Oct 2024 11:24:01 +0200 [thread overview]
Message-ID: <2024101559-spent-unpicked-fde4@gregkh> (raw)
In-Reply-To: <20241015-gpio-class-mountpoint-v2-1-7709301876ef@linaro.org>
On Tue, Oct 15, 2024 at 10:00:23AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Export the address of the /sys/class kobject to users that need to
> chain off of it by means other than calling register_class().
Ick, no.
> This will
> be used by the GPIO subsystem to provide a backward compatibility
> mount-point for the GPIO sysfs class once it's disabled.
Again, ick, no.
No "mount point" should be messing with sysfs, don't do that.
sysfs is a simple "if the file or directory is not there, don't worry
about it" type of interface (i.e. fixing the issues we had with /proc).
If a userspace tool can't find something there, then it should just
error out or move on.
Let's not allow anything to mount anything at /sys/class/ please, that
way lies madness for the next 40+ years. If you want to drop a
userspace api, drop it, don't paper over it with something that you
can't drop either.
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-15 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 8:00 [PATCH v2 0/2] gpio: create the /sys/class/gpio mount point with GPIO_SYSFS disabled Bartosz Golaszewski
2024-10-15 8:00 ` [PATCH v2 1/2] driver core: class: expose the class kobject Bartosz Golaszewski
2024-10-15 9:24 ` Greg Kroah-Hartman [this message]
2024-10-15 8:00 ` [PATCH v2 2/2] gpio: create the /sys/class/gpio mount point with GPIO_SYSFS disabled Bartosz Golaszewski
2024-10-15 9:27 ` Greg Kroah-Hartman
2024-10-15 9:29 ` [PATCH v2 0/2] " Greg Kroah-Hartman
2024-10-15 12:11 ` Bartosz Golaszewski
2024-10-15 12:46 ` Greg Kroah-Hartman
2024-10-15 17:52 ` Bartosz Golaszewski
2024-10-16 7:02 ` Greg Kroah-Hartman
2024-10-16 8:49 ` Bartosz Golaszewski
2024-10-16 9:12 ` Greg Kroah-Hartman
2024-11-12 10:04 ` Bartosz Golaszewski
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=2024101559-spent-unpicked-fde4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=warthog618@gmail.com \
/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