From: Greg KH <gregkh@suse.de>
To: "Moore, Eric" <Eric.Moore@lsil.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
James.Bottomley@SteelEye.com, hch@lst.de
Subject: Re: [PATCH ] drivers/scsi/scsi.c - export reprobe
Date: Tue, 14 Mar 2006 07:35:24 -0800 [thread overview]
Message-ID: <20060314153524.GB8071@suse.de> (raw)
In-Reply-To: <F331B95B72AFFB4B87467BE1C8E9CF5F36D82A@NAMAIL2.ad.lsil.com>
On Mon, Mar 13, 2006 at 05:52:43PM -0700, Moore, Eric wrote:
> Request for exporting device_reprobe -
> This is scsi wrapper portion.
Is this even really needed? It's just a single pointer dereference...
thanks,
greg k-h
next prev parent reply other threads:[~2006-03-14 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 0:52 [PATCH ] drivers/scsi/scsi.c - export reprobe Moore, Eric
2006-03-14 15:35 ` Greg KH [this message]
2006-03-14 16:08 ` Christoph Hellwig
2006-03-14 16:31 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 16:18 Moore, Eric
2006-03-14 22:02 Moore, Eric
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=20060314153524.GB8071@suse.de \
--to=gregkh@suse.de \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox