> obsolete and correctly re-labelled as such. As for the && !HOTPLUG
> menace you keep touting, that might perhaps be applied to some of
> the individual hardware device drivers but certainly not to the
In my tree its just the drivers that still use pci_find_device.
> > Want to be on that. There is nobody maintaining it. That isn't a
> > sustainable situation so it will break.
>
> Not sure I'm following you. There is an official maintainer, and
> although he's currently rather silent on this topic, there's no
> reason to believe he won't step up if there's actually some urgent
> maintaining to be done.
Well once it ends up && BROKEN perhaps patches will appear, or before
that. If not well the pain factor will resolve the problem.
> > No risk of deadlock. It'll progress to && BROKEN which will either cause
> > sufficient pain for someone to get off their arse and fix it, for enough
> > of a vendors users to get the vendor to do the work or for someone who
> > cares to pay a third party to do the work.
>
> Do I sense some hidden agenda there?
No I'm speaking from experience - if a subsystem maintainer is too
busy/working on other projects and the subsystem stops working it
produces a rapid and sudden supply of new maintainers, unless nobody
cares in which case it can go in the bitbucket.
> The isdn4linux subsystem will not "progress" to BROKEN unless
> somebody pushes it there.
It has drivers using functions that will soon be deleted. That isn't so
much as pushing more like getting fed up of pulling someone elses cart
along.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
