public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] add sysfs attributes to scan and delete scsi_devices
Date: Sun, 13 Jul 2003 14:43:19 +0100	[thread overview]
Message-ID: <20030713144319.A24927@infradead.org> (raw)
In-Reply-To: <20030708152440.A373@beaverton.ibm.com>; from patmans@us.ibm.com on Tue, Jul 08, 2003 at 03:24:40PM -0700

On Tue, Jul 08, 2003 at 03:24:40PM -0700, Patrick Mansfield wrote:
> Scanning makes more sense as a host attribute (or as a target attribute,
> but we don't have a target device today).

So we should have a scan host attribute for that.

> Deletion of a scsi_device makes
> more sense as a /sysfs/bus/scsi (or even scsi_device) attribute that takes
> a bus_id. 

I don't think it makes sense as a /sysfs/bus/scsi attribute.  Having
it as a scsi_device attribute makes lots of sense, I just wonder whether
the non-symmetric interface would confuse users.  Probably not too much
as scannaing a bus an deleting a device isn't really a symmetric interface
anyway.`


  reply	other threads:[~2003-07-13 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 20:40 [PATCH] add sysfs attributes to scan and delete scsi_devices Patrick Mansfield
2003-07-08 20:41 ` examples using " Patrick Mansfield
2003-07-08 20:47 ` [PATCH] add " Christoph Hellwig
2003-07-08 22:36   ` Patrick Mansfield
2003-07-08 20:50 ` James Bottomley
2003-07-08 21:13   ` Christoph Hellwig
2003-07-08 22:24     ` Patrick Mansfield
2003-07-13 13:43       ` Christoph Hellwig [this message]
2003-07-09 20:27 ` [PATCH] take 2 " Patrick Mansfield
2003-07-09 20:29   ` and some example usage of the attributes 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=20030713144319.A24927@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --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