From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Set/get accessor cleanups
Date: Mon, 30 Jun 2025 17:54:26 +0200 [thread overview]
Message-ID: <20250630155425.GH31241@twin.jikos.cz> (raw)
In-Reply-To: <2055bb59-b10d-41be-b7f7-f891e4bcac00@gmx.com>
On Sun, Jun 29, 2025 at 10:48:15AM +0930, Qu Wenruo wrote:
> > David Sterba (4):
> > btrfs: don't use token set/get accessors for btrfs_item members
> > btrfs: don't use token set/get accessors in inode.c:fill_inode_item()
> > btrfs: tree-log: don't use token set/get accessors in
> > fill_inode_item()
> > btrfs: accessors: delete token versions of set/get helpers
>
> Looks good to me.
>
> Reviewed-by: Qu Wenruo <wqu@suse.com>
>
> Although it also exposed that we have two different fill_inode_item()
> functions.
> I know the tree log code needs some special handling, the
> fill_inode_item() in inode.c looks like can be implemented by the one in
> tree-log.
>
> It may be a good time to merge them into one in another patch.
Yes, the difference is not that big so it makes sense to merge them.
next prev parent reply other threads:[~2025-06-30 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 14:03 [PATCH 0/4] Set/get accessor cleanups David Sterba
2025-06-27 14:03 ` [PATCH 1/4] btrfs: don't use token set/get accessors for btrfs_item members David Sterba
2025-06-27 14:03 ` [PATCH 2/4] btrfs: don't use token set/get accessors in inode.c:fill_inode_item() David Sterba
2025-06-27 14:03 ` [PATCH 3/4] btrfs: tree-log: don't use token set/get accessors in fill_inode_item() David Sterba
2025-06-27 14:03 ` [PATCH 4/4] btrfs: accessors: delete token versions of set/get helpers David Sterba
2025-06-29 1:13 ` Qu Wenruo
2025-06-30 16:11 ` David Sterba
2025-06-29 1:18 ` [PATCH 0/4] Set/get accessor cleanups Qu Wenruo
2025-06-30 15:54 ` David Sterba [this message]
2025-06-30 6:25 ` 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=20250630155425.GH31241@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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