From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ewan Milne <emilne@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/5] Retry READ CAPACITY(10)/(16) with good status but no data
Date: Tue, 05 Aug 2025 22:22:24 -0400 [thread overview]
Message-ID: <yq14iulb392.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAGtn9r=7+y=QyAS=uVwMp3uVJ_y0Pheepi30eMsH66TRbpVVoA@mail.gmail.com> (Ewan Milne's message of "Fri, 1 Aug 2025 16:51:46 -0400")
Ewan,
> Gentle ping for reviews.
I will take another look once the merge window has closed. But no
objections to the general approach.
Since this constitutes a core change, I would like another reviewer or
two...
--
Martin K. Petersen
prev parent reply other threads:[~2025-08-06 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 18:48 [PATCH 0/5] Retry READ CAPACITY(10)/(16) with good status but no data Ewan D. Milne
2025-07-16 18:48 ` [PATCH 1/5] scsi: sd: Have scsi-ml retry read_capacity_16 errors Ewan D. Milne
2025-08-13 0:22 ` Bart Van Assche
2025-08-13 17:50 ` Bart Van Assche
2025-07-16 18:48 ` [PATCH 2/5] scsi: sd: Avoid passing potentially uninitialized "sense_valid" to read_capacity_error() Ewan D. Milne
2025-08-13 0:02 ` Bart Van Assche
2025-07-16 18:48 ` [PATCH 3/5] scsi: sd: Remove checks for -EOVERFLOW in sd_read_capacity() Ewan D. Milne
2025-08-13 0:04 ` Bart Van Assche
2025-07-16 18:48 ` [PATCH 4/5] scsi: sd: Check for and retry in case of READ_CAPCITY(10)/(16) returning no data Ewan D. Milne
2025-08-13 0:13 ` Bart Van Assche
2025-07-16 18:48 ` [PATCH 5/5] scsi: scsi_debug: Add option to suppress returned data but return good status Ewan D. Milne
2025-08-13 0:16 ` Bart Van Assche
2025-08-01 20:51 ` [PATCH 0/5] Retry READ CAPACITY(10)/(16) with good status but no data Ewan Milne
2025-08-06 2:22 ` Martin K. Petersen [this message]
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=yq14iulb392.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=emilne@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.