From: Dave Jones <davej@suse.de>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
Torrey Hoffman <thoffman@arnor.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: depmod problem for 2.5.2-dj4
Date: Thu, 24 Jan 2002 10:20:02 +0100 [thread overview]
Message-ID: <20020124102002.B10498@suse.de> (raw)
In-Reply-To: <1011744752.2440.0.camel@shire.arnor.net> <20020123045405.GA12060@kroah.com> <20020123094414.D5170@suse.cz> <20020123212435.GB15259@kroah.com> <003701c1a470$86b6bda0$6800000a@brownell.org> <20020124100154.A8622@suse.cz>
In-Reply-To: <20020124100154.A8622@suse.cz>; from vojtech@suse.cz on Thu, Jan 24, 2002 at 10:01:54AM +0100
On Thu, Jan 24, 2002 at 10:01:54AM +0100, Vojtech Pavlik wrote:
> > What's the story on "driverfs" happening, by the way? Last I knew, the
> > PCI bits weren't yet ready.
> I'm not absolutely sure about the status of the PCI support, but it
> should be close to working. Anyway, the driverfs infrastructure itself
> is in place in 2.5, so even if the PCI part wasn't there, still we can
> convert USB and Input to it.
>From pre4 changelog:
- Patrick Mochel: devicefs updates, add PCI devices into the hierarchy
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-24 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 0:12 depmod problem for 2.5.2-dj4 Torrey Hoffman
2002-01-23 4:54 ` Greg KH
2002-01-23 8:44 ` Vojtech Pavlik
2002-01-23 21:24 ` Greg KH
2002-01-23 22:22 ` Greg KH
2002-01-23 22:47 ` Vojtech Pavlik
2002-01-23 23:00 ` Greg KH
2002-01-24 0:46 ` [linux-usb-devel] " David Brownell
2002-01-24 9:01 ` Vojtech Pavlik
2002-01-24 9:20 ` Dave Jones [this message]
2002-01-24 15:27 ` [linux-usb-devel] Re: usb+driverfs [was depmod problem for 2.5.2-dj4] David Brownell
2002-01-24 15:32 ` Vojtech Pavlik
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=20020124102002.B10498@suse.de \
--to=davej@suse.de \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=thoffman@arnor.net \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.