From: Kristian Hogsberg <hogsberg@users.sourceforge.net>
To: Ben Collins <bcollins@debian.org>
Cc: Kristian Hogsberg <hogsberg@users.sourceforge.net>,
Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH] modutils: ieee1394 device_id extraction
Date: 15 Sep 2001 18:28:13 +0200 [thread overview]
Message-ID: <m34rq4mnaa.fsf@dk20037170.bang-olufsen.dk> (raw)
In-Reply-To: <m38zfgmohp.fsf@dk20037170.bang-olufsen.dk> <20010915121233.U8723@visi.net>
In-Reply-To: <20010915121233.U8723@visi.net>
Ben Collins <bcollins@debian.org> writes:
> On Sat, Sep 15, 2001 at 06:02:10PM +0200, Kristian Hogsberg wrote:
> >
> > Hi,
> >
> > I've been adding hotplug support to the ieee1394 subsystem, and the
> > ieee1394 stack in cvs now calls the usermode helper just like usb, pci
> > and the rest of them. Next step is to extend depmod so it extracts
> > the device id tables from the 1394 device drivers, which is exactly
> > what the patch below does.
> >
> > Keith, would you apply this to modutils?
>
> Any ETA on converting the sbp2 driver to the hotplug/nodemgr interfaces?
> I can either sync the current CVS with Linus as-is, or wait till that is
> done, if you think it will be done soon.
I think you should merge it as-is. The sbp2 driver will still work
with the hotplug system, it just does it's own probing now. As for
the ETA, I'll be working on it this weekend, so I hope to have
something ready soon.
Kristian
next prev parent reply other threads:[~2001-09-15 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 16:02 Kristian Hogsberg
2001-09-15 16:12 ` Ben Collins
2001-09-15 16:28 ` Kristian Hogsberg [this message]
2001-09-15 17:40 ` Ben Collins
2001-09-16 8:46 ` Keith Owens
2001-09-16 10:18 ` Kristian Hogsberg
2001-09-17 11:15 ` Artur Frysiak
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=m34rq4mnaa.fsf@dk20037170.bang-olufsen.dk \
--to=hogsberg@users.sourceforge.net \
--cc=bcollins@debian.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®