From: James Bottomley <jejb@linux.vnet.ibm.com>
To: Don Brace <don.brace@microsemi.com>,
joseph.szczypek@hpe.com, gerry.morong@microsemi.com,
john.hall@microsemi.com, Kevin.Barnett@microsemi.com,
Mahesh.Rajashekhara@microsemi.com, bader.alisaleh@microsemi.com,
hch@infradead.org, scott.teel@microsemi.com,
Viswas.G@microsemi.com, Justin.Lindley@microsemi.com,
scott.benesh@microsemi.com, POSWALD@suse.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH V3 2/3] hpsa: limit outstanding rescans
Date: Wed, 15 Mar 2017 10:23:39 -0700 [thread overview]
Message-ID: <1489598619.2387.22.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <148917811749.17050.10796225321668028334.stgit@brunhilda>
On Fri, 2017-03-10 at 14:35 -0600, Don Brace wrote:
> avoid rescan storms. No need to queue another
> if one is pending.
>
> Reviewed-by: Scott Benesh <scott.benesh@microsemi.com>
> Reviewed-by: Scott Teel <scott.teel@microsemi.com>
> Reviewed-by: Tomas Henzl <thenzl@redhat.com> review
Guys, what is this additional "review" for? I just noticed because my
reply scripts barfed on it. Please don't add extra junk after an email
address in a tag line.
Thanks,
James
next prev parent reply other threads:[~2017-03-15 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 20:35 [PATCH V3 0/3] hpsa updates Don Brace
2017-03-10 20:35 ` [PATCH V3 1/3] hpsa: update check for logical volume status Don Brace
2017-03-10 20:35 ` [PATCH V3 2/3] hpsa: limit outstanding rescans Don Brace
2017-03-15 17:23 ` James Bottomley [this message]
2017-03-15 17:32 ` Don Brace
2017-03-15 19:41 ` Martin K. Petersen
2017-03-10 20:35 ` [PATCH V3 3/3] hpsa: do not timeout reset operations Don Brace
2017-03-14 3:00 ` [PATCH V3 0/3] hpsa updates Martin K. Petersen
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=1489598619.2387.22.camel@linux.vnet.ibm.com \
--to=jejb@linux.vnet.ibm.com \
--cc=Justin.Lindley@microsemi.com \
--cc=Kevin.Barnett@microsemi.com \
--cc=Mahesh.Rajashekhara@microsemi.com \
--cc=POSWALD@suse.com \
--cc=Viswas.G@microsemi.com \
--cc=bader.alisaleh@microsemi.com \
--cc=don.brace@microsemi.com \
--cc=gerry.morong@microsemi.com \
--cc=hch@infradead.org \
--cc=john.hall@microsemi.com \
--cc=joseph.szczypek@hpe.com \
--cc=linux-scsi@vger.kernel.org \
--cc=scott.benesh@microsemi.com \
--cc=scott.teel@microsemi.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