From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] btrfs: first batch of zoned cleanups
Date: Tue, 7 Dec 2021 20:12:50 +0100 [thread overview]
Message-ID: <20211207191249.GD28560@twin.jikos.cz> (raw)
In-Reply-To: <cover.1638886948.git.johannes.thumshirn@wdc.com>
On Tue, Dec 07, 2021 at 06:28:33AM -0800, Johannes Thumshirn wrote:
> Here's the first btach of cleanups for the zoned code. In contrast to the 1st
> submission [1] it is a minimalized set of patches with no dependencies on
> other subsystems in btrfs. All of these patches are independant and can be
> applied on their own.
>
> The remaining patches from v1 will be sent out separately, once properly
> reworked.
>
> [1] https://lore.kernel.org/linux-btrfs/cover.1637745470.git.johannes.thumshirn@wdc.com/
>
> Johannes Thumshirn (4):
> btrfs: zoned: encapsulate inode locking for zoned relocation
> btrfs: zoned: simplify btrfs_check_meta_write_pointer
> btrfs: zoned: sink zone check into btrfs_repair_one_zone
> btrfs: zoned: it's pointless to check for REQ_OP_ZONE_APPEND and
> btrfs_is_zoned
Added to misc-next, thanks.
prev parent reply other threads:[~2021-12-07 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 14:28 [PATCH v2 0/4] btrfs: first batch of zoned cleanups Johannes Thumshirn
2021-12-07 14:28 ` [PATCH v2 1/4] btrfs: zoned: encapsulate inode locking for zoned relocation Johannes Thumshirn
2021-12-07 19:08 ` David Sterba
2021-12-08 9:06 ` Johannes Thumshirn
2021-12-08 12:05 ` David Sterba
2021-12-07 14:28 ` [PATCH v2 2/4] btrfs: zoned: simplify btrfs_check_meta_write_pointer Johannes Thumshirn
2021-12-07 14:28 ` [PATCH v2 3/4] btrfs: zoned: sink zone check into btrfs_repair_one_zone Johannes Thumshirn
2021-12-07 14:28 ` [PATCH v2 4/4] btrfs: zoned: it's pointless to check for REQ_OP_ZONE_APPEND and btrfs_is_zoned Johannes Thumshirn
2021-12-07 19:12 ` David Sterba [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=20211207191249.GD28560@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@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