linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Cleanup short int types in block group reserve
Date: Fri, 8 Jul 2022 21:21:20 +0800	[thread overview]
Message-ID: <94010efe-db44-e1c2-b445-61babe9c0893@oracle.com> (raw)
In-Reply-To: <cover.1657220460.git.dsterba@suse.com>



On 08/07/2022 03:02, David Sterba wrote:
> Using the short type in btrfs_block_rsv is not needed for bool
> indicators and we can make the structure smaller.
> 
> v2:
> - fix true/false typo in first patch
> - use named enum for block group type
> 
> David Sterba (3):
>    btrfs: switch btrfs_block_rsv::full to bool
>    btrfs: switch btrfs_block_rsv::failfast to bool
>    btrfs: use enum for btrfs_block_rsv::type
> 
>   fs/btrfs/block-rsv.c   | 21 +++++++++------------
>   fs/btrfs/block-rsv.h   | 15 ++++++++-------
>   fs/btrfs/delayed-ref.c |  4 ++--
>   fs/btrfs/file.c        |  2 +-
>   fs/btrfs/inode.c       |  4 ++--
>   5 files changed, 22 insertions(+), 24 deletions(-)
> 

For the whole series

Reviewed-by: Anand Jain <anand.jain@oracle.com>

  parent reply	other threads:[~2022-07-08 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 19:02 [PATCH v2 0/3] Cleanup short int types in block group reserve David Sterba
2022-07-07 19:02 ` [PATCH v2 1/3] btrfs: switch btrfs_block_rsv::full to bool David Sterba
2022-07-07 19:02 ` [PATCH v2 2/3] btrfs: switch btrfs_block_rsv::failfast " David Sterba
2022-07-07 19:02 ` [PATCH v2 3/3] btrfs: use enum for btrfs_block_rsv::type David Sterba
2022-07-08 13:21 ` Anand Jain [this message]
2022-07-09 11:40 ` [PATCH v2 0/3] Cleanup short int types in block group reserve 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=94010efe-db44-e1c2-b445-61babe9c0893@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 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).