From: Greg KH <gregkh@linuxfoundation.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Christian Brauner <brauner@kernel.org>,
xiangyu.chen@windriver.com, stable-commits@vger.kernel.org,
linux-erofs mailing list <linux-erofs@lists.ozlabs.org>
Subject: Re: Patch "erofs: reliably distinguish block based and fscache mode" has been added to the 6.1-stable tree
Date: Fri, 6 Dec 2024 12:24:32 +0100 [thread overview]
Message-ID: <2024120618-imaging-disgrace-ff35@gregkh> (raw)
In-Reply-To: <bdb479e2-baea-4824-89cd-4449c044e441@linux.alibaba.com>
On Fri, Dec 06, 2024 at 06:37:54PM +0800, Gao Xiang wrote:
>
>
> On 2024/12/6 18:03, Greg KH wrote:
> > On Fri, Dec 06, 2024 at 05:41:11PM +0800, Gao Xiang wrote:
> > > Hi Greg,
> > >
> > > On 2024/12/6 17:33, Greg KH wrote:
> > > > On Fri, Dec 06, 2024 at 01:05:21PM +0800, Gao Xiang wrote:
> > > > > Hi XiangYu,
> > > > >
> > > > > Just noticed that. Why it's needed for Linux 6.1 LTS?
> > > > > Just see my reply, I think 6.1 LTS is not impacted:
> > > > > https://lore.kernel.org/r/686626cd-7dcd-4931-bf55-108522b9bfeb@linux.alibaba.com/
> > > > >
> > > > > Also, it seems some dependenies are missing, just
> > > > > backporting this commit will break EROFS.
> > > > >
> > > > > Hi Greg,
> > > > >
> > > > > Please help drop this patch from 6.1 queue before more
> > > > > explanations, thanks!
> > > >
> > > > Now dropped, sorry about that.
> > >
> > > No need sorry :-) just wonder the cases why we backport
> > > this commit.
> >
> > It was done so explicitly here:
> > https://lore.kernel.org/r/20241129074059.925789-1-xiangyu.chen@eng.windriver.com
> >
> > The submitter should have cc:ed the developers involved, I'll try to
> > poke them to do that in the future.
>
> I received that email but ignored it accidently, I meant
> I just wonder the original reason on the Xiangyu's side.
> Is there something wrong in the production?
I have no idea, Xiangyu would have to answer that.
prev parent reply other threads:[~2024-12-06 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024120228-mocker-refinance-e073@gregkh>
2024-12-06 5:05 ` Patch "erofs: reliably distinguish block based and fscache mode" has been added to the 6.1-stable tree Gao Xiang
2024-12-06 9:33 ` Greg KH
2024-12-06 9:41 ` Gao Xiang
2024-12-06 10:03 ` Greg KH
2024-12-06 10:37 ` Gao Xiang
2024-12-06 11:24 ` 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=2024120618-imaging-disgrace-ff35@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=stable-commits@vger.kernel.org \
--cc=xiangyu.chen@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.