From: Jens Axboe <axboe@kernel.dk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] driver core: remove CONFIG_SYSFS_DEPRECATED and CONFIG_SYSFS_DEPRECATED_V2
Date: Thu, 23 Feb 2023 09:04:32 -0700 [thread overview]
Message-ID: <36c3acf2-dd51-f8a5-47d0-043848639cf0@kernel.dk> (raw)
In-Reply-To: <20230223073326.2073220-1-gregkh@linuxfoundation.org>
On 2/23/23 12:33 AM, Greg Kroah-Hartman wrote:
> CONFIG_SYSFS_DEPRECATED was added in commit 88a22c985e35
> ("CONFIG_SYSFS_DEPRECATED") in 2006 to allow systems with older versions
> of some tools (i.e. Fedora 3's version of udev) to boot properly. Four
> years later, in 2010, the option was attempted to be removed as most of
> userspace should have been fixed up properly by then, but some kernel
> developers clung to those old systems and refused to update, so we added
> CONFIG_SYSFS_DEPRECATED_V2 in commit e52eec13cd6b ("SYSFS: Allow boot
> time switching between deprecated and modern sysfs layout") to allow
> them to continue to boot properly, and we allowed a boot time parameter
> to be used to switch back to the old format if needed.
>
> Over time, the logic that was covered under these config options was
> slowly removed from individual driver subsystems successfully, removed,
> and the only thing that is now left in the kernel are some changes in
> the block layer's representation in sysfs where real directories are
> used instead of symlinks like normal.
>
> Because the original changes were done to userspace tools in 2006, and
> all distros that use those tools are long end-of-life, and older
> non-udev-based systems do not care about the block layer's sysfs
> representation, it is time to finally remove this old logic and the
> config entries from the kernel.
Acked-by: Jens Axboe <axboe@kernel.dk>
--
Jens Axboe
prev parent reply other threads:[~2023-02-23 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 7:33 Greg Kroah-Hartman
2023-02-23 16:04 ` Jens Axboe [this message]
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=36c3acf2-dd51-f8a5-47d0-043848639cf0@kernel.dk \
--to=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®