From: Patrick Mansfield <patmans@us.ibm.com>
To: Andries.Brouwer@cwi.nl
Cc: greg@kroah.com, mdharm-usb@one-eyed-alien.net,
linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: sysfs
Date: Mon, 13 Jan 2003 17:30:51 -0800 [thread overview]
Message-ID: <20030113173051.A18731@beaverton.ibm.com> (raw)
In-Reply-To: <UTC200301140109.h0E196W01345.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Tue, Jan 14, 2003 at 02:09:06AM +0100
On Tue, Jan 14, 2003 at 02:09:06AM +0100, Andries.Brouwer@cwi.nl wrote:
> > It looks like there is a missing scsi_set_device() call in scsiglue.c,
>
> OK, added. Now rmmod usb-storage followed by insmod usb-storage
> resulted in an oops, as usual, but after a fresh reboot:
> Yes indeed, just like desired:
>
> % ls -l /sysfs/block/sdb/device
> ... -> ../../devices/pci0/00:07.2/usb1/1-2/1-2.4/1-2.4.1/2:0:0:0
>
> Good.
> Now that you removed this scsi device from /sysfs/devices, I suppose
> you'll also want to remove
>
> /sysfs/devices/1:0:6:0
>
> which is an Iomega ZIP drive on the parallel port, driver imm.c,
> device sda.
> (I can also do it but have no time now. Friday.)
>
> All the best - Andries
I don't know and have not used the parport code, it needs to be ported to
sysfs before we could simply call scsi_set_device() call in imm.c, or
maybe have a /sysfs/scsi/pseudo added via scsi_add_host(shost, NULL) or a
/sysfs/scsi/unported, similiar to was discussed on the linux-scsi thread
"[PATCH] allow NULL dev argument to scsi_add_host":
http://marc.theaimsgroup.com/?t=104231385300005&r=1&w=2
-- Patrick Mansfield
next prev parent reply other threads:[~2003-01-14 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 1:09 sysfs Andries.Brouwer
2003-01-14 1:30 ` Patrick Mansfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 14:43 sysfs Andries.Brouwer
2003-01-14 0:27 ` sysfs Patrick Mansfield
2003-01-14 0:51 ` sysfs Matthew Dharm
2003-01-14 0:57 ` sysfs Greg KH
2003-01-14 0:56 ` sysfs Greg KH
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=20030113173051.A18731@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=mochel@osdl.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 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.