From: Greg KH <gregkh@linuxfoundation.org>
To: Yang Bo <yyyeer.bo@gmail.com>
Cc: stable@vger.kernel.org, linux-fsdevel@vger.kernel.org,
mszeredi@redhat.com, Yang Bo <yb203166@antfin.com>
Subject: Re: [PATCH 0/6] Backport several patches to 5.10.y
Date: Tue, 18 Apr 2023 12:34:44 +0200 [thread overview]
Message-ID: <2023041850-slicing-ancient-8203@gregkh> (raw)
In-Reply-To: <20230412041935.1556-1-yb203166@antfin.com>
On Wed, Apr 12, 2023 at 12:19:29PM +0800, Yang Bo wrote:
> Antgroup is using 5.10.y in product environment, we found several patches are
> missing in 5.10.y tree. These patches are needed for us. So we backported them
> to 5.10.y
As many of these are also missing in the 5.15.y and 6.1.y trees, we can
only take these if you have a series for all kernel trees as you do not
want anyone upgrading to a newer kernel tree and having a regression.
So please fix this up by sending patch series for all of the relevant
trees and then we can queue them up all at the same time.
thanks,
greg k-h
prev parent reply other threads:[~2023-04-18 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 4:19 [PATCH 0/6] Backport several patches to 5.10.y Yang Bo
2023-04-12 4:19 ` [PATCH 1/6] virtiofs: clean up error handling in virtio_fs_get_tree() Yang Bo
2023-04-12 4:19 ` [PATCH 2/6] virtiofs: split requests that exceed virtqueue size Yang Bo
2023-04-12 4:19 ` [PATCH 3/6] fuse: check s_root when destroying sb Yang Bo
2023-04-12 4:19 ` [PATCH 4/6] fuse: fix attr version comparison in fuse_read_update_size() Yang Bo
2023-04-12 4:19 ` [PATCH 5/6] fuse: always revalidate rename target dentry Yang Bo
2023-04-12 4:19 ` [PATCH 6/6] fuse: fix deadlock between atomic O_TRUNC and page invalidation Yang Bo
2023-04-18 10: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=2023041850-slicing-ancient-8203@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yb203166@antfin.com \
--cc=yyyeer.bo@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