Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: linux-scsi@vger.kernel.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 0/3] Improve error handling
Date: Tue, 15 Sep 2020 20:29:24 -0400	[thread overview]
Message-ID: <yq1tuvy1s5r.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200910074843.217661-1-damien.lemoal@wdc.com> (Damien Le Moal's message of "Thu, 10 Sep 2020 16:48:40 +0900")


Damien,

> A small series to improve command error hadling.
>
> The first patch is a simple code cleanup. The second patch updates
> asc/ascq sense codes list. Finally, the third patch adds zone resource
> errors handling for zoned block deives to return BLK_STS_DEV_RESOURCE,
> similarly to what the NVMe driver does for ZNS devices.

Applied 1+2 to 5.10/scsi-staging. I'll wait to see where the BLK_STS
stuff lands before applying patch 3. Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2020-09-16  0:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  7:48 [PATCH v2 0/3] Improve error handling Damien Le Moal
2020-09-10  7:48 ` [PATCH v2 1/3] scsi: Cleanup scsi_noretry_cmd() Damien Le Moal
2020-09-10  8:05   ` Johannes Thumshirn
2020-09-10 15:45   ` Himanshu Madhani
2020-09-10  7:48 ` [PATCH v2 2/3] scsi: update additional sense codes list Damien Le Moal
2020-09-10  8:08   ` Johannes Thumshirn
2020-09-10 15:46   ` Himanshu Madhani
2020-09-10  7:48 ` [PATCH v2 3/3] scsi: handle zone resources errors Damien Le Moal
2020-09-10 15:46   ` Himanshu Madhani
2020-09-16  0:29 ` Martin K. Petersen [this message]
2020-09-16  1:11   ` [PATCH v2 0/3] Improve error handling Damien Le Moal
2020-09-22  3:56 ` 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=yq1tuvy1s5r.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=damien.lemoal@wdc.com \
    --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