From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: sd_zbc: update write pointer offset cache
Date: Wed, 17 Mar 2021 07:45:35 +0000 [thread overview]
Message-ID: <PH0PR04MB7416ADF8D9CC7F0600292A5D9B6A9@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: yq15z1q36eh.fsf@ca-mkp.ca.oracle.com
On 17/03/2021 02:42, Martin K. Petersen wrote:
>
> Johannes,
>
>> Martin ping?
>
> When I originally read the thread I was left with the impression that we
> were just papering over an underlying blk-mq issue. However, I read the
> whole thing again and feel this fix is acceptable.
>
Should I resend the patch with the Fixes line applied, or can you take it as is?
next prev parent reply other threads:[~2021-03-17 7:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 9:48 [PATCH] scsi: sd_zbc: update write pointer offset cache Johannes Thumshirn
2021-03-10 22:45 ` Damien Le Moal
2021-03-11 3:14 ` Shinichiro Kawasaki
2021-03-11 15:13 ` Bart Van Assche
2021-03-11 15:18 ` Johannes Thumshirn
2021-03-11 15:48 ` Bart Van Assche
2021-03-11 15:54 ` Johannes Thumshirn
2021-03-12 2:56 ` Bart Van Assche
2021-03-12 4:38 ` Shinichiro Kawasaki
2021-03-12 5:51 ` Johannes Thumshirn
2021-03-12 7:27 ` Damien Le Moal
2021-03-12 7:59 ` Johannes Thumshirn
2021-03-12 8:20 ` Damien Le Moal
2021-03-12 8:58 ` Johannes Thumshirn
2021-03-12 10:05 ` Shinichiro Kawasaki
2021-03-12 10:28 ` Johannes Thumshirn
2021-03-12 11:48 ` Shinichiro Kawasaki
2021-03-12 12:02 ` Johannes Thumshirn
2021-03-16 7:53 ` Johannes Thumshirn
2021-03-17 1:42 ` Martin K. Petersen
2021-03-17 7:45 ` Johannes Thumshirn [this message]
2021-03-19 2:21 ` Martin K. Petersen
2021-03-19 3:45 ` Martin K. Petersen
2021-03-19 8:15 ` Johannes Thumshirn
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=PH0PR04MB7416ADF8D9CC7F0600292A5D9B6A9@PH0PR04MB7416.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shinichiro.kawasaki@wdc.com \
/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;
as well as URLs for NNTP newsgroup(s).