From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Vasu Dev <vasu.dev@intel.com>
Cc: linux-scsi@vger.kernel.org,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
James Smart <james.smart@emulex.com>,
Mike Christie <michaelc@cs.wisc.edu>,
Robert Love <robert.w.love@intel.com>,
Christof Schmitt <christof.schmitt@de.ibm.com>
Subject: Re: [PATCH 00/10] handles queue_depth adjustments in scsi_error.c
Date: Tue, 13 Oct 2009 16:59:27 -0500 [thread overview]
Message-ID: <1255471167.2855.502.camel@localhost.localdomain> (raw)
In-Reply-To: <20090903221910.24946.39993.stgit@vi1.jf.intel.com>
On Thu, 2009-09-03 at 15:22 -0700, Vasu Dev wrote:
> This patch series moves the QUEUE_FULL and then the ramp
> up code from drivers like qla2xxx and lpfc to scsi-ml.
> The change_queue_depth callback is used to allow the
> drivers to adjust the queue depth, so LLDs do not have
> to worry about parsing the sense, see some additional
> info on these changes in first RFC cover at:-
>
> http://www.spinics.net/lists/linux-scsi/msg35959.html
>
> I've tested this series with libfc/fcoe for queue_depth
> ramp down and up.
>
> This series is based on scsi-misc -rc7 and also cleanly
> applies & works on top recently submitted 64 fcoe patches
> series by Rob "[PATCH 00/64] libfc, libfcoe and fcoe
> updates for scsi-misc"
>
> I'm posting this series with Mike and Christof patches
> per this mail thread discussion
> http://marc.info/?l=linux-scsi&m=125196587107768&w=2
>
> Signed-off-by: Vasu Dev <vasu.dev@intel.com>
OK, so this patch series isn't bisectable. If I just apply 1 it won't
compile.
To get to bisectability it looks like patches 1,3,4 need combining. It
also looks like 5,6,7 are all really the same change, so could be
combined.
Could you repost with at least the bisectability fixed?
Thanks,
James
next prev parent reply other threads:[~2009-10-13 22:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 22:22 [PATCH 00/10] handles queue_depth adjustments in scsi_error.c Vasu Dev
2009-09-03 22:22 ` [PATCH 01/10] scsi-ml: modify change_queue_depth to take in reason why it is being called Vasu Dev
2009-09-03 22:22 ` [PATCH 02/10] scsi error: have scsi-ml call change_queue_depth to handle QUEUE_FULL Vasu Dev
2009-09-13 0:52 ` [PATCH 02/10 v2] " Vasu Dev
2009-09-03 22:22 ` [PATCH 03/10] drivers: convert drivers setting the change_queue_depth callback Vasu Dev
2009-09-10 22:22 ` [PATCH 03/10 v2] " Vasu Dev
2009-09-03 22:22 ` [PATCH 04/10] drivers: convert fc drivers calling scsi_track_queue_full Vasu Dev
2009-09-04 13:47 ` Alex.Iannicelli
2009-09-04 21:43 ` Vasu Dev
2009-09-11 16:18 ` Mike Christie
2009-09-11 23:25 ` Vasu Dev
2009-09-14 17:09 ` Mike Christie
[not found] ` <4AAE78DD.9070808-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2009-09-14 22:56 ` Vasu Dev
[not found] ` <1252968994.2231.16.camel-B2RhF0yJhE275v1z/vFq2g@public.gmane.org>
2009-09-15 4:18 ` Mike Christie
2009-09-11 16:54 ` Mike Christie
2009-09-11 20:00 ` Giridhar Malavali
2009-09-07 20:44 ` [PATCH v2] drivers: convert libfc " Vasu Dev
2009-09-03 22:22 ` [PATCH 05/10] scsi: updates sdev to add queue_depth ramp up code Vasu Dev
2009-09-03 22:22 ` [PATCH 06/10] scsi: adds sdev->queue_ramp_up_period to sysfs Vasu Dev
2009-09-03 22:23 ` [PATCH 07/10] scsi: add common queue_depth ramp up code Vasu Dev
2009-09-11 16:31 ` Mike Christie
2009-09-11 23:45 ` Vasu Dev
2009-09-03 22:23 ` [PATCH 08/10] fcoe, libfc: fix an libfc issue with queue ramp down in libfc Vasu Dev
2009-09-10 22:15 ` Robert Love
2009-09-03 22:23 ` [PATCH 09/10] libfc: adds queue_depth ramp up to libfc Vasu Dev
2009-09-10 22:18 ` Robert Love
2009-09-03 22:23 ` [PATCH 10/10] zfcp: Adapt change_queue_depth for queue full tracking Vasu Dev
2009-10-13 21:59 ` James Bottomley [this message]
2009-10-15 23:09 ` [PATCH 00/10] handles queue_depth adjustments in scsi_error.c Vasu Dev
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=1255471167.2855.502.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=andrew.vasquez@qlogic.com \
--cc=christof.schmitt@de.ibm.com \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=robert.w.love@intel.com \
--cc=vasu.dev@intel.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