From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <Damien.LeMoal@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Subject: Re: [PATCH v2 0/2] null_blk cleanup and fix
Date: Tue, 21 Apr 2020 11:38:04 -0600 [thread overview]
Message-ID: <ebd01ecd-0e4f-9a23-3dfb-d11f9c3e0771@kernel.dk> (raw)
In-Reply-To: <BY5PR04MB69002C510DECF1439C33FD32E7D50@BY5PR04MB6900.namprd04.prod.outlook.com>
On 4/21/20 3:10 AM, Damien Le Moal wrote:
> Jens,
>
> On 2020/04/01 10:07, Damien Le Moal wrote:
>> Jens,
>>
>> The first patch of this series extracts and extends a fix included in
>> the zone append series to correctly handle writes to null_blk zoned
>> devices. The fix forces zone type and zone condition checks to be
>> executed before the generic null_blk bad block and memory backing
>> options handling. The fix also makes sure that a zone write pointer
>> position is updated only if these two generic operations are executed
>> successfully.
>>
>> The second patch is from Johannes series for REQ_OP_ZONE_APPEND support
>> to clean up null_blk zoned device initialization. The reviewed tag
>> from Christoph sent for the patch within Johannes post is included here.
>>
>> Please consider these patches for inclusion in 5.7.
Can you respin for block-5.7? The series doesn't apply.
--
Jens Axboe
prev parent reply other threads:[~2020-04-21 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 1:07 [PATCH v2 0/2] null_blk cleanup and fix Damien Le Moal
2020-04-01 1:07 ` [PATCH v2 1/2] block: null_blk: Fix zoned command handling Damien Le Moal
2020-04-01 1:52 ` Chaitanya Kulkarni
2020-04-01 9:34 ` Christoph Hellwig
2020-04-01 1:07 ` [PATCH v2 2/2] null_blk: Cleanup zoned device initialization Damien Le Moal
2020-04-01 1:31 ` Chaitanya Kulkarni
2020-04-21 9:10 ` [PATCH v2 0/2] null_blk cleanup and fix Damien Le Moal
2020-04-21 17:38 ` Jens Axboe [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=ebd01ecd-0e4f-9a23-3dfb-d11f9c3e0771@kernel.dk \
--to=axboe@kernel.dk \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).