From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 150 release
Date: Thu, 07 Jan 2010 18:12:09 +0000 [thread overview]
Message-ID: <20100107181209.GA17743@kroah.com> (raw)
In-Reply-To: <1262883808.2430.1.camel@yio.site>
On Thu, Jan 07, 2010 at 07:07:29PM +0100, Kay Sievers wrote:
> On Thu, Jan 7, 2010 at 18:33, Greg KH <greg@kroah.com> wrote:
> >> udev 150
> >> ====
> >> Bugfixes.
> >>
> >> Kernels with SYSFS_DEPRECATED=y are not supported since a while. Many users
> >> depend on the current sysfs layout and the information not available in the
> >> deprecated layout. All remaining support for the deprecated sysfs layout is
> >> removed now.
> >
> > Nice, we should start to work on removing this option in the kernel now
> > as well.
>
> Yeah, that would be awesome, and make the "subsystem patch", which
> cleans up the last weirdness in sysfs, the artificial split between
> classes and buses, really really simple. :)
I would like that.
Anyone remember what udev version that is needed if we remove that
kernel option? I'll try to dig through the different distros to see if
it is yet safe to remove.
And the subsystem merge would be good to have as well, I see the crap
that various android drivers are doing with sysfs and want to keep that
from propagating into the mainline kernel. The subsystem stuff should
stop most of that.
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-07 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 17:03 [ANNOUNCE] udev 150 release Kay Sievers
2010-01-07 17:33 ` Greg KH
2010-01-07 18:07 ` Kay Sievers
2010-01-07 18:12 ` Greg KH [this message]
2010-01-07 18:32 ` Robby Workman
2010-01-07 19:37 ` Greg KH
2010-01-07 19:56 ` Robby Workman
2010-01-08 16:29 ` Greg KH
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=20100107181209.GA17743@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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 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).