From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/5] SCSI scanning and removal fixes
Date: Wed, 07 Sep 2005 10:26:16 -0500 [thread overview]
Message-ID: <1126106776.4823.18.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0507261012340.4746-100000@iolanthe.rowland.org>
On Tue, 2005-07-26 at 10:18 -0400, Alan Stern wrote:
> This patch (as543) adds a private entry point to scsi_scan_target, for use
> when the caller already owns the scan_mutex, and updates the kerneldoc for
> that routine (which was badly out-of-date). It converts scsi_scan_channel
> to use the new entry point. Lastly, it modifies scsi_get_host_dev to make
> it acquire the scan_mutex, necessary since the routine adds a new
> scsi_device even if it doesn't do any actual scanning.
This looks fine, thanks,
James
prev parent reply other threads:[~2005-09-07 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 14:18 [PATCH 2/5] SCSI scanning and removal fixes Alan Stern
2005-09-07 15:26 ` James Bottomley [this message]
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=1126106776.4823.18.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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