public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs: qgroup API cleanups
Date: Wed, 18 Mar 2026 14:12:51 +1030	[thread overview]
Message-ID: <ec6daf90-7ebc-4468-a0bc-a3c0ef87f300@gmx.com> (raw)
In-Reply-To: <cover.1773776354.git.fdmanana@suse.com>



在 2026/3/18 06:16, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Remove some unnecessary qgroup functions and exports and make the API
> simpler.

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> 
> Filipe Manana (4):
>    btrfs: removed unused qgroup functions for pertrans reservation and freeing
>    btrfs: collapse __btrfs_qgroup_free_meta() into btrfs_qgroup_free_meta_prealloc()
>    btrfs: collapse __btrfs_qgroup_reserve_meta() into btrfs_qgroup_reserve_meta_prealloc()
>    btrfs: unexport btrfs_qgroup_reserve_meta()
> 
>   fs/btrfs/delayed-inode.c |  3 +--
>   fs/btrfs/qgroup.c        | 27 ++++++++++++++------------
>   fs/btrfs/qgroup.h        | 42 +++-------------------------------------
>   3 files changed, 19 insertions(+), 53 deletions(-)
> 


      parent reply	other threads:[~2026-03-18  3:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 19:46 [PATCH 0/4] btrfs: qgroup API cleanups fdmanana
2026-03-17 19:47 ` [PATCH 1/4] btrfs: removed unused qgroup functions for pertrans reservation and freeing fdmanana
2026-03-17 19:47 ` [PATCH 2/4] btrfs: collapse __btrfs_qgroup_free_meta() into btrfs_qgroup_free_meta_prealloc() fdmanana
2026-03-17 19:47 ` [PATCH 3/4] btrfs: collapse __btrfs_qgroup_reserve_meta() into btrfs_qgroup_reserve_meta_prealloc() fdmanana
2026-03-17 19:47 ` [PATCH 4/4] btrfs: unexport btrfs_qgroup_reserve_meta() fdmanana
2026-03-18  3:42 ` Qu Wenruo [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=ec6daf90-7ebc-4468-a0bc-a3c0ef87f300@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=fdmanana@kernel.org \
    --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