From: Ewan Milne <emilne@redhat.com>
To: Rob Evers <revers@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH V6 0/3] scsi: Configure number of LUs reported by 'report-luns'
Date: Mon, 05 Jan 2015 09:59:52 -0500 [thread overview]
Message-ID: <1420469992.3891.94.camel@localhost.localdomain> (raw)
In-Reply-To: <1418745680-18126-1-git-send-email-revers@redhat.com>
On Tue, 2014-12-16 at 11:01 -0500, Rob Evers wrote:
> This patch set retrieves the number of LUs available on a target
> using the report-luns command by re-sizing the returned data
> buffer and retrying report luns.
>
> A minor bug fix is included.
>
> scsi_mod parameter max_report_luns is no longer used and is removed.
>
> Changes from previous posting:
>
> - remove exteraneous else
>
> - remove INITIAL_MAX_REPORT_LUNS, hardwire buffer sizing, and touch up
> related comment
>
> Rob Evers (3):
> scsi: Avoid unnecessary GFP_ATOMIC allocation in scsi_report_lun_scan
> scsi: Use set/get_unaligned_be32 in report_luns
> scsi: retry report-luns when reported LU count requres more memory
>
> drivers/scsi/scsi_scan.c | 54 ++++++++++++++----------------------------------
> 1 file changed, 15 insertions(+), 39 deletions(-)
>
Looks good.
Reviewed-by: Ewan D. Milne <emilne@redhat.com>
next prev parent reply other threads:[~2015-01-05 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 16:01 [PATCH V6 0/3] scsi: Configure number of LUs reported by 'report-luns' Rob Evers
2014-12-16 16:01 ` [PATCH V6 1/3] scsi: Avoid unnecessary GFP_ATOMIC allocation in scsi_report_lun_scan Rob Evers
2014-12-16 16:01 ` [PATCH V6 2/3] scsi: Use set/get_unaligned_be32 in report_luns Rob Evers
2014-12-16 16:01 ` [PATCH V6 3/3] scsi: retry report-luns when reported LU count requres more memory Rob Evers
2015-01-05 14:59 ` Ewan Milne [this message]
2015-01-05 19:25 ` [PATCH V6 0/3] scsi: Configure number of LUs reported by 'report-luns' 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=1420469992.3891.94.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=revers@redhat.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