From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: modutils 2.4.2, please test asap
Date: Mon, 22 Jan 2001 19:37:47 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98019228421662@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98018911111962@msgid-missing>
Keith Owens wrote:
> Please test this modutils patch ASAP, at least one distribution is
> waiting to burn their master CD for kernel 2.4.0. Remove
> patch-2.4.0-hotplug from the kernel if you have installed it.
>
> This patch is being released under protest. It completely drops
> support for USB device ids on kernel 2.4.0-prerelease and earlier.
> That will break USB support for anybody who installs modutils 2.4.2 and
> tries to run a kernel before 2.4.0.
>
> Breaking backwards compatibility goes completely against the grain for
> modutils. It goes to a lot of bother to support users on older kernels
> and to ensure that any mix of new modutils and old kernels will work,
> even down to kernel 2.0. But since the USB maintainers are refusing to
> support USB on anything older than 2.4.0, I have no choice but to break
> backwards compatibility.
Hey. Let's be fair here. Linus rejected your patch for reasons that
had absolutely nothing to do with USB backport support issues.
Rather, the kernel version tracking was rejected because Linus wants
that functionality added in 2.5 in a careful manner. I'm not saying
your patch wasn't perfect and thoughtful. I thought your patch looked
great, but I don't control kernel checkins.
Regarding the USB backport support, the usbd and kernel policy stuff
that David Brownell and others develops works great for that environment.
There are several important functional holes in the backport. One of them
being in the USB Storage area. If I understand this correctly, these are
holes that are intrinsic to the older kernel and are not easily worked
around. All that to say that noone using a 2.2 kernel is going to be
in USB nirvana anyhow, though it works quite well.
Be assured, I'll be delighted when Linus accepts your patch and
modutils can support kernel version tracking so that modutils can
better support and handle ABI changes. We are all just rolling with
Linus. He is calling the shots, here.
I appreciate you getting this functional change into 2.4.2 so that
USB users in the 2.4.0 series can use hotplugging. I'll test your patch
immediately.
Best wishes,
Miles
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-22 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 18:24 modutils 2.4.2, please test asap Keith Owens
2001-01-22 19:28 ` Keith Owens
2001-01-22 19:37 ` Miles Lane [this message]
2001-01-22 19:58 ` Stephen J. Gowdy
2001-01-22 20:05 ` Miles Lane
2001-01-22 20:16 ` Johannes Erdfelt
2001-01-22 20:30 ` David Brownell
2001-01-22 21:40 ` Keith Owens
2001-01-22 22:29 ` Johannes Erdfelt
2001-01-22 22:51 ` Keith Owens
2001-01-22 23:09 ` Greg KH
2001-01-22 23:21 ` David Brownell
2001-01-22 23:38 ` Miles Lane
2001-01-22 23:42 ` Keith Owens
2001-01-23 2:52 ` David Brownell
2001-01-23 3:25 ` Keith Owens
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=marc-linux-hotplug-98019228421662@msgid-missing \
--to=miles@megapathdsl.net \
--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).