From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.2 bcdDevice munging patch
Date: Tue, 04 Dec 2001 03:49:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100743779310331@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100743001825350@msgid-missing>
Sounds fair to me. Though it'll need to be a bit smarter, since I
think the current code says "if the kernel is 2.2 then ..." and it'd
have to change to handle two types of 2.2 kernels (original, new).
That is, the newer 2.2 kernels would need updated hotplug scripts.
- Dave
----- Original Message -----
From: "Greg KH" <greg@kroah.com>
To: "Plato" <tom@redant.freeserve.co.uk>
Cc: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Monday, December 03, 2001 7:32 PM
Subject: Re: 2.2 bcdDevice munging patch
> On Tue, Dec 04, 2001 at 01:44:59AM +0000, Plato wrote:
> > > The attached patch seeks to rectify this. Please let me know if it is any
> > > use and whether or not it will be included in your releases.
> >
> > Hmmm ... here it is. This time :-)
>
> I'd recommend fixing the 2.2 kernel code to work the same way as 2.4.x.
> The hotplug code was enabled right at the end of the 2.2.20 development
> cycle, and this problem must have slipped through.
>
> thanks,
>
> greg k-h
>
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-12-04 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 1:41 2.2 bcdDevice munging patch Plato
2001-12-04 1:44 ` Plato
2001-12-04 3:32 ` Greg KH
2001-12-04 3:49 ` David Brownell [this message]
2001-12-05 0:42 ` Plato
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-100743779310331@msgid-missing \
--to=david-b@pacbell.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).