All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
	James.Smart@Emulex.Com, linux-scsi@vger.kernel.org,
	Mark Haverkamp <markh@osdl.org>
Subject: Re: [PATCH] LLDD dynamic scan aids
Date: Thu, 18 Nov 2004 07:48:14 -0800	[thread overview]
Message-ID: <20041118154814.GA8553@us.ibm.com> (raw)
In-Reply-To: <20041118143644.GA23365@infradead.org>

On Thu, Nov 18, 2004 at 02:36:44PM +0000, Christoph Hellwig wrote:
> On Thu, Nov 18, 2004 at 09:32:09AM -0500, Salyzyn, Mark wrote:
> > But scsi_rescan_device and scsi_scan_host_selected both target specific
> > ids though? As long as we stay away from the wildcards for
> > scsi_scan_host_selected, or am I mistaken?
> 
> scsi_rescan_device should be exported.  For the target scan something
> like the second hunk of James' patch looks good to me.

Why not export scsi_scan_host_selected (and SCAN_WILD_CARD)? If a driver
used it wrong then change the driver.

Suppose a driver wants to scan a given channel. (Would one ever want to
scan for a particular a LUN? I can't think of a reason).

If the driver wants to rescan the host (it knows it it has already
called any scsi scan functions), it would call:

	scsi_scan_host_selected(shost, SCAN_WILD_CARD,
		SCAN_WILD_CARD, SCAN_WILD_CARD, 1);

And new target scan:

	scsi_scan_host_selected(shost, chan, id, SCAN_WILD_CARD, 0);

Target rescan:

	scsi_scan_host_selected(shost, chan, id, SCAN_WILD_CARD, 1);

Instead of any shost->rescan logic.

-- Patrick Mansfield

  reply	other threads:[~2004-11-18 15:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 14:32 [PATCH] LLDD dynamic scan aids Salyzyn, Mark
2004-11-18 14:36 ` Christoph Hellwig
2004-11-18 15:48   ` Patrick Mansfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-29 17:28 Mukker, Atul
2004-11-19 21:07 Mukker, Atul
2004-11-18 15:32 James.Smart
2004-11-18 15:43 ` Christoph Hellwig
2004-11-18 15:07 Salyzyn, Mark
2004-11-18 14:11 Salyzyn, Mark
2004-11-18 14:26 ` Christoph Hellwig
2004-11-18 13:36 James.Smart
2004-11-18 14:23 ` Christoph Hellwig
2004-11-17 19:03 James.Smart
2004-11-18 10:46 ` Christoph Hellwig

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=20041118154814.GA8553@us.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=James.Smart@Emulex.Com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=markh@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.