From: Mike Anderson <andmike@us.ibm.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Douglas Gilbert <dougg@torque.net>,
Andries.Brouwer@cwi.nl, James.Bottomley@steeleye.com,
linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
mdharm-scsi@one-eyed-alien.net
Subject: Re: [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code
Date: Mon, 5 May 2003 10:46:02 -0700 [thread overview]
Message-ID: <20030505174602.GA3433@beaverton.ibm.com> (raw)
In-Reply-To: <20030505093834.B7831@beaverton.ibm.com>
Patrick Mansfield [patmans@us.ibm.com] wrote:
> An sgid user program that does the same thing as the code removed from the
> kernel would be very usefull. This could likely be incorporated into other
> schemes (udev), independent of other details.
>
> Right now, we could have an sgid that runs whenever an sg is found (sg
> hotplug generated via device_register), and stores a sysfs path and the id
> returned into a flat file.
I believe devlabel's scsi_unique_id.c file does some of this, though I
have not looked at it closely.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-05-05 17:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:47 [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code Andries.Brouwer
2003-05-05 7:58 ` Douglas Gilbert
2003-05-05 14:17 ` James Bottomley
2003-05-05 15:52 ` Mike Anderson
2003-05-05 16:14 ` James Bottomley
2003-05-05 16:26 ` Patrick Mansfield
2003-05-05 16:57 ` Mike Anderson
2003-05-05 17:01 ` James Bottomley
2003-05-05 16:38 ` Patrick Mansfield
2003-05-05 16:59 ` James Bottomley
2003-05-05 17:46 ` Mike Anderson [this message]
2003-05-05 22:51 ` Patrick Mansfield
2003-05-06 1:39 ` Douglas Gilbert
2003-05-06 4:11 ` Patrick Mansfield
2003-05-06 5:58 ` Douglas Gilbert
2003-05-06 21:11 ` Patrick Mansfield
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 0:22 Patrick Mansfield
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=20030505174602.GA3433@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
/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