From: David Sterba <dsterba@suse.cz>
To: bingjing chang <bxxxjxxg@gmail.com>
Cc: Filipe Manana <fdmanana@kernel.org>,
bingjingc <bingjingc@synology.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robbie Ko <robbieko@synology.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] btrfs: send: fix failures when processing inodes with no links
Date: Thu, 18 Aug 2022 15:46:43 +0200 [thread overview]
Message-ID: <20220818134643.GL13489@twin.jikos.cz> (raw)
In-Reply-To: <CAMmgxWFpRRp_gGXXncBzoJgsmmbfdtBtfysntW7JpxFBxBNPJQ@mail.gmail.com>
On Fri, Aug 12, 2022 at 10:36:38PM +0800, bingjing chang wrote:
> > I seriously doubt that those 4 commits are the only dependencies in
> > order to be able to cleanly backport to 4.9 and other old branches.
> >
> > It may be better to backport only to a few younger stable branches, or
> > just provide later a version of the patch to
> > apply to each desired stable branch (once the fix is in Linus' tree
> > and in a -rc release).
> >
> > If you are not interested in backporting to stable or don't have the
> > time to verify the dependencies and test, then just remove all the
> > stable tags.
> > Just leave a fixes tag:
> >
> > Fixes: 31db9f7c23fbf7 ("Btrfs: introduce BTRFS_IOC_SEND for btrfs send/receive")
>
> Since backporting is not our goal. I will just leave the fix tag here.
This Fixes: points to the original send patch, so that's not really
useful, otherwise if there's a target stable release where the patches
still apply cleanly, or with minimal conflicts it's sufficient to add a
CC: stable tag it's good to have it.
next prev parent reply other threads:[~2022-08-18 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 10:09 [PATCH v2 0/2] btrfs: send: fix failures when processing inodes with no links bingjingc
2022-08-11 10:09 ` [PATCH v2 1/2] btrfs: send: refactor get_inode_info() bingjingc
2022-08-11 10:09 ` [PATCH v2 2/2] btrfs: send: fix failures when processing inodes with no links bingjingc
2022-08-11 12:00 ` Filipe Manana
2022-08-12 14:36 ` bingjing chang
2022-08-12 16:28 ` Filipe Manana
2022-08-18 13:46 ` David Sterba [this message]
2022-09-22 10:08 ` Filipe Manana
2022-09-23 14:16 ` bingjing chang
2022-09-23 15:32 ` Filipe Manana
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=20220818134643.GL13489@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bingjingc@synology.com \
--cc=bxxxjxxg@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robbieko@synology.com \
--cc=stable@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).