public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Qu Wenruo <wqu@suse.com>
Cc: dsterba@suse.com, nborisov@suse.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] btrfs: enhance unsupported compat RO flags handling" failed to apply to 4.9-stable tree
Date: Mon, 17 Oct 2022 11:34:47 +0200	[thread overview]
Message-ID: <Y00ht3ZPNYzKlLss@kroah.com> (raw)
In-Reply-To: <20403694-0d4f-38b3-643b-c09e745f4bd8@suse.com>

On Mon, Oct 17, 2022 at 06:59:00AM +0800, Qu Wenruo wrote:
> 
> 
> On 2022/10/16 20:25, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.9-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> Thanks for the mail, I'll backport the patch manually.
> 
> Just want to praise the new dependency hints.
> 
> > 
> > Possible dependencies:
> > 
> > 81d5d61454c3 ("btrfs: enhance unsupported compat RO flags handling")
> > dfe8aec4520b ("btrfs: add a btrfs_block_group_root() helper")
> > b6e9f16c5fda ("btrfs: replace open coded while loop with proper construct")
> > 42437a6386ff ("btrfs: introduce mount option rescue=ignorebadroots")
> > 68319c18cb21 ("btrfs: show rescue=usebackuproot in /proc/mounts")
> > ab0b4a3ebf14 ("btrfs: add a helper to print out rescue= options")
> > ceafe3cc3992 ("btrfs: sysfs: export supported rescue= mount options")
> > 334c16d82cfe ("btrfs: push the NODATASUM check into btrfs_lookup_bio_sums")
> > d70bf7484f72 ("btrfs: unify the ro checking for mount options")
> > 7573df5547c0 ("btrfs: sysfs: export supported send stream version")
> > 3ef3959b29c4 ("btrfs: don't show full path of bind mounts in subvol=")
> > 74ef00185eb8 ("btrfs: introduce "rescue=" mount option")
> > e3ba67a108ff ("btrfs: factor out reading of bg from find_frist_block_group")
> > 89d7da9bc592 ("btrfs: get mapping tree directly from fsinfo in find_first_block_group")
> > c730ae0c6bb3 ("btrfs: convert comments to fallthrough annotations")
> > aeb935a45581 ("btrfs: don't set SHAREABLE flag for data reloc tree")
> > 92a7cc425223 ("btrfs: rename BTRFS_ROOT_REF_COWS to BTRFS_ROOT_SHAREABLE")
> > 3be4d8efe3cf ("btrfs: block-group: rename write_one_cache_group()")
> > 97f4728af888 ("btrfs: block-group: refactor how we insert a block group item")
> > 7357623a7f4b ("btrfs: block-group: refactor how we delete one block group item")
> 
> It looks so awesome!!
> 
> I'm wondering how this is implemented? It would definitely help backporting
> not only to stable, but also some vendor backports branches.

Sasha's scripts generate these and put them online and you can do:
	curl --fail --silent https://git.kernel.org/pub/scm/linux/kernel/git/sashal/deps.git/plain/v$STABLE_VERSION/$git_id

to query the dependancy tree.

thanks,

greg k-h

      reply	other threads:[~2022-10-17  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 12:25 FAILED: patch "[PATCH] btrfs: enhance unsupported compat RO flags handling" failed to apply to 4.9-stable tree gregkh
2022-10-16 22:59 ` Qu Wenruo
2022-10-17  9:34   ` Greg KH [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=Y00ht3ZPNYzKlLss@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dsterba@suse.com \
    --cc=nborisov@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=wqu@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