Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "bart.vanassche@gmail.com" <bart.vanassche@gmail.com>,
	"hch@infradead.org" <hch@infradead.org>,
	"himanshu.madhani@cavium.com" <himanshu.madhani@cavium.com>,
	"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
	"nab@linux-iscsi.org" <nab@linux-iscsi.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"giridhar.malavali@cavium.com" <giridhar.malavali@cavium.com>
Subject: Re: [PATCH 03/11] qla2xxx: Make trace flags more readable.
Date: Wed, 11 Jan 2017 20:47:01 +0000	[thread overview]
Message-ID: <1484167606.2619.23.camel@sandisk.com> (raw)
In-Reply-To: <1482553419-4117-4-git-send-email-himanshu.madhani@cavium.com>

On Fri, 2016-12-23 at 20:23 -0800, Himanshu Madhani wrote:
> From: Quinn Tran <quinn.tran@cavium.com>
> 
> This patch does not change any functionality.

Please also mention in the patch description what the purpose of cmd_flags
is. If I remember correctly the only purpose of most flags is to make
analyzing crash dumps easier?

Bart.

  parent reply	other threads:[~2017-01-11 20:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-24  4:23 [PATCH 00/11] qla2xxx: Feature updates for target Himanshu Madhani
2016-12-24  4:23 ` [PATCH 01/11] qla2xxx: Remove direct access of scsi_status field in se_cmd Himanshu Madhani
2016-12-24  4:23 ` [PATCH 02/11] qla2xxx: Cleanup TMF code translation from qla_target Himanshu Madhani
2017-01-11 20:05   ` Bart Van Assche
2017-01-11 20:43     ` Madhani, Himanshu
2017-01-11 21:08   ` Bart Van Assche
2017-01-11 23:01     ` Madhani, Himanshu
2016-12-24  4:23 ` [PATCH 03/11] qla2xxx: Make trace flags more readable Himanshu Madhani
2017-01-09 13:11   ` Christoph Hellwig
2017-01-09 18:36     ` Madhani, Himanshu
2017-01-11 20:47   ` Bart Van Assche [this message]
2017-01-11 20:54     ` Madhani, Himanshu
2016-12-24  4:23 ` [PATCH 04/11] qla2xxx: Cleanup SRR code Himanshu Madhani
2017-01-09 13:13   ` Christoph Hellwig
2017-01-10 17:55     ` Madhani, Himanshu
2016-12-24  4:23 ` [PATCH 05/11] qla2xxx: Fix wrong argument in sp done callback Himanshu Madhani
2017-01-09 13:17   ` Christoph Hellwig
2017-01-09 18:05     ` Madhani, Himanshu
2016-12-24  4:23 ` [PATCH 06/11] qla2xxx: Use d_id instead of s_id for more clarity Himanshu Madhani
2017-01-09 13:17   ` Christoph Hellwig
2016-12-24  4:23 ` [PATCH 07/11] qla2xxx: Track I-T nexus as single fc_port struct Himanshu Madhani
2017-01-09 13:28   ` Christoph Hellwig
2016-12-24  4:23 ` [PATCH 08/11] qla2xxx: Add framework for Async fabric discovery Himanshu Madhani
2017-01-11 20:08   ` Bart Van Assche
2017-01-13 17:50     ` Madhani, Himanshu
2016-12-24  4:23 ` [PATCH 09/11] qla2xxx: Add Dual mode support in the driver Himanshu Madhani
2017-01-11 19:51   ` Bart Van Assche
2017-01-13 22:13     ` Madhani, Himanshu
2016-12-24  4:23 ` [PATCH 10/11] qla2xxx: Remove unused reverse_ini_mode Himanshu Madhani
2016-12-24  4:23 ` [PATCH 11/11] qla2xxx: Improve RSCN handling in driver Himanshu Madhani
2017-01-11 21:05   ` Bart Van Assche

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=1484167606.2619.23.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=bart.vanassche@gmail.com \
    --cc=giridhar.malavali@cavium.com \
    --cc=hch@infradead.org \
    --cc=himanshu.madhani@cavium.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=target-devel@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