mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Daniel Vacek <neelx@suse.com>, Chris Mason <clm@fb.com>,
	Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: extent buffer flags cleanup
Date: Wed, 26 Mar 2025 08:06:52 +1030	[thread overview]
Message-ID: <f32db2c5-fe4b-4152-ae36-f48175e7e64c@gmx.com> (raw)
In-Reply-To: <20250325163139.878473-1-neelx@suse.com>



在 2025/3/26 03:01, Daniel Vacek 写道:
> There are a few leftover extent buffer flags not being meaningfully used
> anymore for some time. Simply clean them up.

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

Thanks,
Qu


>
> Daniel Vacek (3):
>    btrfs: cleanup EXTENT_BUFFER_READ_ERR flag
>    btrfs: cleanup EXTENT_BUFFER_READAHEAD flag
>    btrfs: cleanup EXTENT_BUFFER_CORRUPT flag
>
>   fs/btrfs/disk-io.c     | 11 ++---------
>   fs/btrfs/extent-tree.c |  6 ------
>   fs/btrfs/extent_io.c   |  7 ++-----
>   fs/btrfs/extent_io.h   |  5 -----
>   4 files changed, 4 insertions(+), 25 deletions(-)
>


  parent reply	other threads:[~2025-03-25 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 16:31 Daniel Vacek
2025-03-25 16:31 ` [PATCH 1/3] btrfs: cleanup EXTENT_BUFFER_READ_ERR flag Daniel Vacek
2025-03-25 16:31 ` [PATCH 2/3] btrfs: cleanup EXTENT_BUFFER_READAHEAD flag Daniel Vacek
2025-03-25 16:31 ` [PATCH 3/3] btrfs: cleanup EXTENT_BUFFER_CORRUPT flag Daniel Vacek
2025-03-25 21:36 ` Qu Wenruo [this message]
2025-03-27 16:58 ` [PATCH 0/3] btrfs: extent buffer flags cleanup David Sterba

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=f32db2c5-fe4b-4152-ae36-f48175e7e64c@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelx@suse.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
all inboxes | Powered by JetHome®