public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: ZhengYuan Huang <gality369@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: dsterba@suse.com, clm@fb.com, linux-btrfs@vger.kernel.org,
	 linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
	r33s3n6@gmail.com,  zzzccc427@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: reloc: unlink orphan reloc roots before dropping them
Date: Tue, 10 Mar 2026 17:43:10 +0800	[thread overview]
Message-ID: <CAOmEq9UNR3ykGP6exskiJLQpUT36xe91aAs_4Jk8mNvEfNkJ8g@mail.gmail.com> (raw)
In-Reply-To: <4e697f30-1057-451c-9238-5ea748dd3236@suse.com>

On Tue, Mar 10, 2026 at 5:33 PM Qu Wenruo <wqu@suse.com> wrote:
> I just grabbed one from Johannes:
>
> https://lore.kernel.org/linux-btrfs/20260224125113.14831-1-johannes.thumshirn@wdc.com/
>
> And from Filipe:
>
> https://lore.kernel.org/linux-btrfs/b99cee6ce652b926463a080ef052a2e8e37bff33.1772105193.git.fdmanana@suse.com/
>
> And myself, which is more aligned to your style:
>
> https://lore.kernel.org/linux-btrfs/4170e39bac4a2559ad0535f9bd74a89bc44a36d4.1771488629.git.wqu@suse.com/

Thanks a lot for the clarification and for the example patches.

This is very helpful. I understand the changelog expectations much
better now, especially for crash/KASAN fixes. I'll study the examples
you linked and use them as references for future submissions.

Thanks again for the guidance.

Thanks,
ZhengYuan Huang

      reply	other threads:[~2026-03-10  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  7:54 [PATCH] btrfs: reloc: unlink orphan reloc roots before dropping them ZhengYuan Huang
2026-03-10  8:12 ` Qu Wenruo
2026-03-10  8:41   ` ZhengYuan Huang
2026-03-10  9:33     ` Qu Wenruo
2026-03-10  9:43       ` ZhengYuan Huang [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=CAOmEq9UNR3ykGP6exskiJLQpUT36xe91aAs_4Jk8mNvEfNkJ8g@mail.gmail.com \
    --to=gality369@gmail.com \
    --cc=baijiaju1990@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r33s3n6@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=wqu@suse.com \
    --cc=zzzccc427@gmail.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