Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Sun YangKai <sunk67188@gmail.com>
To: dsterba@suse.cz
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: goto out -> return conversions for previous patch
Date: Sat, 04 Oct 2025 20:49:08 +0800	[thread overview]
Message-ID: <5045431.31r3eYUQgx@saltykitkat> (raw)
In-Reply-To: <20251002155611.GI4052@twin.jikos.cz>

> On Thu, Oct 02, 2025 at 09:39:00PM +0800, Sun YangKai wrote:
> > Tested with btrfs/auto group. Tests that require $SCRATCH_DEV_POOL,
> > $LOGWRITES_DEV, zoned block devices and dm flakey support are skipped.
> 
> Is this a standalone patch or fixup to the path auto freeing? The
> changelog should describe the change, not what you tested it on. This
> may matter in some cases but this is better under the "---" line in the
> patch.

Sorry. This is a fixup to the previous path auto freeing patch. I'll resend the 
patches with corrected message later.

> 
> > Signed-off-by: Sun YangKai <sunk67188@gmail.com>
> > ---
> 
> (here)
> 
> >  fs/btrfs/uuid-tree.c | 102 +++++++++++++++----------------------------
> >  fs/btrfs/verity.c    |  14 +++---
> >  fs/btrfs/volumes.c   |  98 +++++++++++++++--------------------------
> >  fs/btrfs/xattr.c     |  29 ++++--------
> >  4 files changed, 86 insertions(+), 157 deletions(-)





      reply	other threads:[~2025-10-04 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  5:09 [PATCH] btrfs: more trivial BTRFS_PATH_AUTO_FREE conversions Sun YangKai
2025-09-30 16:35 ` David Sterba
2025-10-01 13:32   ` Sun YangKai
2025-10-02 13:39   ` [PATCH] btrfs: goto out -> return conversions for previous patch Sun YangKai
2025-10-02 15:56     ` David Sterba
2025-10-04 12:49       ` Sun YangKai [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=5045431.31r3eYUQgx@saltykitkat \
    --to=sunk67188@gmail.com \
    --cc=dsterba@suse.cz \
    --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