From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagig@mellanox.com>
Cc: target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v2 3/3] target: Use scsi helpers to build the sense data correctly
Date: Mon, 6 Jul 2015 02:06:54 -0700 [thread overview]
Message-ID: <20150706090654.GC15996@infradead.org> (raw)
In-Reply-To: <1436169747-28834-4-git-send-email-sagig@mellanox.com>
On Mon, Jul 06, 2015 at 11:02:27AM +0300, Sagi Grimberg wrote:
> Instead of open coding the sense buffer construction, use
> scsi scsi_build_sense_buffer() and scsi_set_sense_information()
> helpers which moved to scsi_common.
>
> This patch also fixes wrong setting of descriptor format sense data
> for t10-pi integrity errors.
Please split this into three patches:
1) move the helpers to scsi_common.c
2) use helpers in the target code
3) always use descriptor-type sense data for PI errors
next prev parent reply other threads:[~2015-07-06 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 8:02 [PATCH v2 0/3] Target sense data handling modifications Sagi Grimberg
2015-07-06 8:02 ` [PATCH v2 1/3] target: Inline transport_get_sense_codes() Sagi Grimberg
2015-07-06 8:59 ` Christoph Hellwig
2015-07-06 12:28 ` Sagi Grimberg
2015-07-06 8:02 ` [PATCH v2 2/3] target: Split transport_send_check_condition_and_sense() Sagi Grimberg
2015-07-06 9:05 ` Christoph Hellwig
2015-07-06 8:02 ` [PATCH v2 3/3] target: Use scsi helpers to build the sense data correctly Sagi Grimberg
2015-07-06 9:06 ` Christoph Hellwig [this message]
2015-07-06 12:29 ` Sagi Grimberg
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=20150706090654.GC15996@infradead.org \
--to=hch@infradead.org \
--cc=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=sagig@mellanox.com \
--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