Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"himanshu.madhani@cavium.com" <himanshu.madhani@cavium.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v3 00/15] qla2xxx: Cleanup and minor fixes
Date: Fri, 2 Jun 2017 23:32:40 +0000	[thread overview]
Message-ID: <1496446359.3881.2.camel@sandisk.com> (raw)
In-Reply-To: <20170602161207.6660-1-himanshu.madhani@cavium.com>

On Fri, 2017-06-02 at 09:11 -0700, Himanshu Madhani wrote:
> This series contains patches that were dropped from 4.12.0-rc3 inclusion, since
> they can go to 4.13 merge window.
> 
> Changes from v2 --> v3
> o Added Reviewed-by tag from Bart. 
> o Droped couple patches for rework. 
> o Addressed minor comments from Bart where applicable. 
> 
> Changes from v1 --> v2
> o Addressed 0-day kernel warning.
> o Addressed cleanups and updates as per Bart's comments.
> o Added Acked-by tag from Nicholas to applicable patches.
> 
> Please apply this series to for-next branch to be included in 4.13 merge window.

Hello Martin and Himanshu,

All comments I had posted on this patch series have been addressed so I'm fine
with this patch series.

Bart.

  parent reply	other threads:[~2017-06-02 23:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 16:11 [PATCH v3 00/15] qla2xxx: Cleanup and minor fixes Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 01/15] qla2xxx: Allow ABTS, PURX, RIDA on ATIOQ for ISP83XX/27XX Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 02/15] qla2xxx: Replace usage of spin_lock with spin_lock_irqsave Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 03/15] qla2xxx: Retain loop test for fwdump length exceeding buffer length Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 04/15] qla2xxx: Fix path recovery Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 05/15] tcm_qla2xxx: Do not allow aborted cmd to advance Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 06/15] qla2xxx: Use flag PFLG_DISCONNECTED Himanshu Madhani
2017-06-02 16:11 ` [PATCH v3 07/15] qla2xxx: Convert 32-bit LUN usage to 64-bit Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 08/15] qla2xxx: Fix name server relogin Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 09/15] qla2xxx: Cleanup debug message IDs Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 10/15] qla2xxx: Turn on FW option for exchange check Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 11/15] qla2xxx: Add ql2xiniexchg parameter Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 12/15] qla2xxx: Remove redundant wait when target is stopped Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 13/15] qla2xxx: Accelerate SCSI BUSY status generation in target mode Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 14/15] qla2xxx: Remove unused irq_cmd_count field Himanshu Madhani
2017-06-02 16:12 ` [PATCH v3 15/15] qla2xxx: Remove extra register read Himanshu Madhani
2017-06-02 23:32 ` Bart Van Assche [this message]
2017-06-03  0:38 ` [PATCH v3 00/15] qla2xxx: Cleanup and minor fixes 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=1496446359.3881.2.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=himanshu.madhani@cavium.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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