public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
	Andries.Brouwer@cwi.nl, afafc@rnl.ist.utl.pt,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	greg@kroah.com, SCSI Mailing List <linux-scsi@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net, mike@hingston.demon.co.uk,
	stelian@popies.net, torvalds@transmeta.com
Subject: Re: [example PATCH - not for applying] exclude certain commands
Date: Thu, 24 Apr 2003 14:43:03 -0700	[thread overview]
Message-ID: <20030424144303.A2730@beaverton.ibm.com> (raw)
In-Reply-To: <20030424135932.D10511@one-eyed-alien.net>; from mdharm-scsi@one-eyed-alien.net on Thu, Apr 24, 2003 at 01:59:32PM -0700

On Thu, Apr 24, 2003 at 01:59:32PM -0700, Matthew Dharm wrote:
> On Thu, Apr 24, 2003 at 04:20:50PM -0400, James Bottomley wrote:

> > I think the evpd code can be thrown out into user land (where the rules
> > governing how it's used can be much more flexible).  All we really use
> > it for is to get a unique name.  However, even WWN inquiries don't
> > always guarantee even that...
> 
> Well, I'd love to see a patch to do that.  But I seem to recall someone
> being opposed to that idea.... maybe I'm just imagining that.

I wanted it to stay for scsi mid-level multi-path usage, but multi-path
isn't in the kernel, and if multi-path wants to use it in-kernel, we can
carry the deleted code as a patch or better yet use some sort of
user-initiated scanning (maybe not full user scsi scanning for now, just
something that allows synchronized user intervention to get/set id's
between the scsi_scan_host and the scsi_attach_device calls.)

And we want some sort of id for udev, but that can be done in user space.

So kill it before it's too late.

-- Patrick Mansfield

  reply	other threads:[~2003-04-24 21:34 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 18:59 [example PATCH - not for applying] exclude certain commands Andries.Brouwer
2003-04-24 19:14 ` Matthew Dharm
2003-04-24 20:20   ` James Bottomley
2003-04-24 20:59     ` Matthew Dharm
2003-04-24 21:43       ` Patrick Mansfield [this message]
2003-04-24 21:09     ` [linux-usb-devel] " Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2003-04-27  2:29 Andries.Brouwer
2003-04-27  4:32 ` James Bottomley
2003-04-26 21:44 Andries.Brouwer
2003-04-26 22:13 ` Matthew Dharm
2003-04-26 22:43   ` James Bottomley
2003-04-27  1:34     ` Matthew Dharm
2003-04-27  2:15       ` James Bottomley
2003-04-27  9:35         ` Matthew Dharm
2003-04-27 15:41           ` James Bottomley
2003-04-27 18:52             ` Kai Makisara
2003-04-27 19:52             ` Matthew Dharm
2003-04-28 19:05               ` Luben Tuikov
2003-04-28 19:12                 ` Luben Tuikov
2003-04-28 20:19                 ` Matthew Dharm
2003-04-28 21:33                   ` Luben Tuikov
2003-04-26 22:29 ` James Bottomley
2003-04-27  0:24   ` Patrick Mansfield
2003-04-27  1:39   ` Matthew Dharm
2003-04-25  0:43 Andries.Brouwer
2003-04-25  2:12 ` Matthew Dharm
2003-04-25 14:32 ` Alan Stern
2003-04-25 15:12   ` Oliver Neukum
2003-04-26  0:58     ` Alan Stern
2003-04-26  8:24       ` Oliver Neukum
2003-04-26 15:22         ` Alan Stern
2003-04-24 15:21 Andries.Brouwer
2003-04-24 15:56 ` Pete
2003-04-24 21:33 ` Stelian Pop
2003-04-24  9:46 Andries.Brouwer
2003-04-24  9:56 ` Stelian Pop
2003-04-24 14:05 ` Alan Stern
2003-04-24 14:26   ` James Bottomley
2003-04-24 14:46     ` Alan Stern
2003-04-24 15:26       ` James Bottomley
2003-04-24  9:08 Andries.Brouwer
2003-04-24 18:22 ` Matthew Dharm
2003-04-23 22:39 Andries.Brouwer
2003-04-24  0:10 ` Matthew Dharm
2003-04-24  8:05 ` André Cruz
2003-04-24  9:15 ` Stelian Pop
2003-04-24  9:22   ` Stelian Pop
2003-04-24 11:45 ` Mike Bursell
2003-04-24 12:44 ` James Bottomley

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=20030424144303.A2730@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=James.Bottomley@SteelEye.com \
    --cc=afafc@rnl.ist.utl.pt \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mike@hingston.demon.co.uk \
    --cc=stelian@popies.net \
    --cc=torvalds@transmeta.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