From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <damien.lemoal@wdc.com>, linux-block@vger.kernel.org
Cc: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH v3 0/2] null_blk cleanup and fix
Date: Thu, 23 Apr 2020 09:35:48 -0600 [thread overview]
Message-ID: <263f6213-6732-0c21-28aa-e97aa0db7a41@kernel.dk> (raw)
In-Reply-To: <20200423030238.494843-1-damien.lemoal@wdc.com>
On 4/22/20 9:02 PM, 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.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-04-23 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 3:02 [PATCH v3 0/2] null_blk cleanup and fix Damien Le Moal
2020-04-23 3:02 ` [PATCH v3 1/2] null_blk: Fix zoned command handling Damien Le Moal
2020-04-23 7:14 ` Johannes Thumshirn
2020-04-23 3:02 ` [PATCH v3 2/2] null_blk: Cleanup zoned device initialization Damien Le Moal
2020-04-23 15:35 ` 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=263f6213-6732-0c21-28aa-e97aa0db7a41@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 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.