From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Parameter cleanup
Date: Fri, 21 Oct 2022 10:42:14 +0800 [thread overview]
Message-ID: <767b18dc-3ee2-1678-2780-ca78e99fd1d7@oracle.com> (raw)
In-Reply-To: <cover.1666285085.git.dsterba@suse.com>
On 21/10/2022 00:59, David Sterba wrote:
> A few more cases where value passed by parameter can be used directly.
>
> v2:
> - move related code from patch 2 to patch 1
>
> David Sterba (4):
> btrfs: sink gfp_t parameter to btrfs_backref_iter_alloc
> btrfs: sink gfp_t parameter to btrfs_qgroup_trace_extent
> btrfs: switch GFP_NOFS to GFP_KERNEL in scrub_setup_recheck_block
> btrfs: sink gfp_t parameter to alloc_scrub_sector
For the series:
Reviewed-by: Anand Jain <anand.jain@oracle.com>
>
> fs/btrfs/backref.c | 5 ++---
> fs/btrfs/backref.h | 3 +--
> fs/btrfs/qgroup.c | 17 +++++++----------
> fs/btrfs/qgroup.h | 2 +-
> fs/btrfs/relocation.c | 2 +-
> fs/btrfs/scrub.c | 14 +++++++-------
> fs/btrfs/tree-log.c | 3 +--
> 7 files changed, 20 insertions(+), 26 deletions(-)
>
next prev parent reply other threads:[~2022-10-21 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:59 [PATCH v2 0/4] Parameter cleanup David Sterba
2022-10-20 16:59 ` [PATCH v2 1/4] btrfs: sink gfp_t parameter to btrfs_backref_iter_alloc David Sterba
2022-10-20 16:59 ` [PATCH v2 2/4] btrfs: sink gfp_t parameter to btrfs_qgroup_trace_extent David Sterba
2022-10-20 16:59 ` [PATCH v2 3/4] btrfs: switch GFP_NOFS to GFP_KERNEL in scrub_setup_recheck_block David Sterba
2022-10-20 16:59 ` [PATCH v2 4/4] btrfs: sink gfp_t parameter to alloc_scrub_sector David Sterba
2022-10-21 2:42 ` Anand Jain [this message]
2022-10-21 8:07 ` [PATCH v2 0/4] Parameter cleanup 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=767b18dc-3ee2-1678-2780-ca78e99fd1d7@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.