From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernek.dk, linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: sense handling improvements
Date: Wed, 15 Feb 2017 22:42:56 -0500 [thread overview]
Message-ID: <yq18tp6by2n.fsf@oracle.com> (raw)
In-Reply-To: <20170214191600.17480-1-hch@lst.de> (Christoph Hellwig's message of "Tue, 14 Feb 2017 20:15:54 +0100")
>>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:
Christoph> this series is on top of the scsi_request changes in Jens'
Christoph> tree and further improves the handling of the sense buffer.
Very nice cleanup!
Christoph> The first patch prevents any possibily of reusing stale sense
Christoph> codes in sense headers, and is a bug fix that we should
Christoph> probably get into the block tree ASAP.
Christoph> The rest cleans up handling of the parsed sense data and
Christoph> could go in either through the block tree, or a SCSI branch
Christoph> on top of the block tree.
I can bring them in after Linus' initial block pull.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-02-16 3:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 19:15 sense handling improvements Christoph Hellwig
2017-02-14 19:15 ` [PATCH 1/6] scsi: always zero sshdr in scsi_normalize_sense Christoph Hellwig
2017-02-15 7:59 ` Hannes Reinecke
2017-02-14 19:15 ` [PATCH 2/6] sd: improve TUR handling in sd_check_events Christoph Hellwig
2017-02-15 8:00 ` Hannes Reinecke
2017-02-14 19:15 ` [PATCH 3/6] scsi: make the sense header argument to scsi_test_unit_ready mandatory Christoph Hellwig
2017-02-14 19:15 ` [PATCH 4/6] scsi: simplify scsi_execute_req_flags Christoph Hellwig
2017-02-14 19:15 ` [PATCH 5/6] scsi: merge __scsi_execute into scsi_execute Christoph Hellwig
2017-02-14 19:16 ` [PATCH 6/6] scsi: remove scsi_execute_req_flags Christoph Hellwig
2017-02-15 8:19 ` sense handling improvements Hannes Reinecke
2017-02-15 15:04 ` Christoph Hellwig
2017-02-15 15:30 ` Bart Van Assche
2017-02-16 3:42 ` Martin K. Petersen [this message]
2017-02-16 14:33 ` Christoph Hellwig
2017-02-22 7:19 ` Christoph Hellwig
2017-02-22 13:52 ` Martin K. Petersen
2017-02-23 0:51 ` Martin K. Petersen
2017-02-23 9:49 ` Christoph Hellwig
2017-02-23 14:28 ` Martin K. Petersen
2017-02-23 14:31 ` Christoph Hellwig
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=yq18tp6by2n.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernek.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@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