From: Jocelyn Mayer <jma@netgem.com>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ieee1394 sbp2 driver is broken for kernel >= 2.4.21-rc2
Date: 03 Jun 2003 23:12:34 +0200 [thread overview]
Message-ID: <1054674754.4951.184.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <20030603132504.C21083@one-eyed-alien.net>
On Tue, 2003-06-03 at 22:25, Matthew Dharm wrote:
> I know jumping in the middle of a conversation is bad, but....
>
> In conversations with the SBP2 folks, they indicated to me that the way
> they do hotplugging is very different from the way usb-storage does it.
> The end result (I'm told) is that invoking a scan from userspace is often
> needed for SBP2 but never for usb-storage.
>
> So, comparing the two is really pointless.
>
> Matt
>
Hi,
you're right, I just wanted to point that there's no reason
that we need to register a device etheir by hand or using
an "infamous script" (citation from Ben Collins
http://sourceforge.net/mailarchive/message.php?msg_id=4435485 )
due to the SCSI stack, but that it's only a SBP2 problem.
Regards.
next prev parent reply other threads:[~2003-06-03 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 19:36 [BUG] ieee1394 sbp2 driver is broken for kernel >= 2.4.21-rc2 Jocelyn Mayer
2003-06-02 20:34 ` Georg Nikodym
2003-06-02 21:20 ` Jocelyn Mayer
2003-06-03 11:36 ` Ben Collins
2003-06-03 18:11 ` Jocelyn Mayer
2003-06-03 18:27 ` Georg Nikodym
2003-06-03 19:01 ` Jocelyn Mayer
2003-06-03 19:34 ` Richard B. Johnson
2003-06-03 18:54 ` Ben Collins
2003-06-03 20:20 ` Jocelyn Mayer
2003-06-03 19:26 ` Ben Collins
2003-06-03 21:12 ` Jocelyn Mayer
2003-06-03 19:28 ` Ben Collins
2003-06-03 20:25 ` Matthew Dharm
2003-06-03 21:12 ` Jocelyn Mayer [this message]
2003-06-03 23:01 ` Matthew Dharm
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=1054674754.4951.184.camel@jma1.dev.netgem.com \
--to=jma@netgem.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.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;
as well as URLs for NNTP newsgroup(s).