Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: remove unused arguments and code in block-rsv.c
Date: Thu, 1 Oct 2026 18:38:11 +0930	[thread overview]
Message-ID: <95cca09f-70ca-444a-b8c9-a1f6af81fac4@suse.com> (raw)
In-Reply-To: <cover.1790783086.git.fdmanana@suse.com>



在 2026/10/1 01:17, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Remove unnecessary code and arguments from a few functions in block-rsv.c.

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

Thanks,
Qu

> 
> Filipe Manana (3):
>    btrfs: remove fs_info argument from btrfs_block_rsv_add()
>    btrfs: remove fs_info argument from btrfs_block_rsv_refill()
>    btrfs: remove pointless qgroup assignment in block_rsv_release_bytes()
> 
>   fs/btrfs/block-group.c   |  5 ++---
>   fs/btrfs/block-rsv.c     | 12 +++---------
>   fs/btrfs/block-rsv.h     |  6 ++----
>   fs/btrfs/delayed-inode.c |  3 +--
>   fs/btrfs/inode.c         |  4 ++--
>   fs/btrfs/props.c         |  3 +--
>   fs/btrfs/relocation.c    | 13 +++++--------
>   fs/btrfs/root-tree.c     |  3 +--
>   fs/btrfs/transaction.c   |  3 +--
>   9 files changed, 18 insertions(+), 34 deletions(-)
> 


      parent reply	other threads:[~2026-10-01  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 15:47 [PATCH 0/3] btrfs: remove unused arguments and code in block-rsv.c fdmanana
2026-09-30 15:47 ` [PATCH 1/3] btrfs: remove fs_info argument from btrfs_block_rsv_add() fdmanana
2026-09-30 15:47 ` [PATCH 2/3] btrfs: remove fs_info argument from btrfs_block_rsv_refill() fdmanana
2026-09-30 15:47 ` [PATCH 3/3] btrfs: remove pointless qgroup assignment in block_rsv_release_bytes() fdmanana
2026-10-01  9:08 ` 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=95cca09f-70ca-444a-b8c9-a1f6af81fac4@suse.com \
    --to=wqu@suse.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