From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v5 0/8] btrfs: use fs_holder_ops for btrfs
Date: Wed, 25 Jun 2025 16:31:38 +0200 [thread overview]
Message-ID: <20250625143138.GA31241@twin.jikos.cz> (raw)
In-Reply-To: <cover.1750724841.git.wqu@suse.com>
On Tue, Jun 24, 2025 at 10:02:37AM +0930, Qu Wenruo wrote:
> [CHANGELOG]
> v5:
> - Fix a tailing whitespace
> This introduced by patch "btrfs: add comments to make super block
> creation more clear", and that patch is created during a small
> window where my commit checkpatch hook is broken.
>
> And unfortunately that comment is also later updated by several
> patches, causing several conflicts with that whitespace error fixed.
Thanks, patches added to linux-next again.
prev parent reply other threads:[~2025-06-25 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 0:32 [PATCH v5 0/8] btrfs: use fs_holder_ops for btrfs Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 1/8] btrfs: always open the device read-only in btrfs_scan_one_device Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 2/8] btrfs: get rid of the re-entry of btrfs_get_tree() Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 3/8] btrfs: add comments to make super block creation more clear Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 4/8] btrfs: call btrfs_close_devices from ->kill_sb Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 5/8] btrfs: call bdev_fput() to reclaim the blk_holder immediately Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 6/8] btrfs: delay btrfs_open_devices() until super block is created Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 7/8] btrfs: use the super_block as holder when mounting file systems Qu Wenruo
2025-06-24 0:32 ` [PATCH v5 8/8] btrfs: use fs_holder_ops for all opened devices Qu Wenruo
2025-06-25 14:31 ` 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=20250625143138.GA31241@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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).