[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190618054709.GA4271@kroah.com>
Date: Tue, 18 Jun 2019 07:47:09 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Gao Xiang <gaoxiang25@...wei.com>
Cc: devel@...verdev.osuosl.org, Miao Xie <miaoxie@...wei.com>,
chao@...nel.org, LKML <linux-kernel@...r.kernel.org>,
weidu.du@...wei.com, Fang Wei <fangwei1@...wei.com>,
linux-fsdevel@...r.kernel.org, linux-erofs@...ts.ozlabs.org
Subject: Re: [RFC PATCH 0/8] staging: erofs: decompression inplace approach
On Tue, Jun 18, 2019 at 09:47:08AM +0800, Gao Xiang wrote:
>
>
> On 2019/6/18 4:36, Greg Kroah-Hartman wrote:
> > On Sat, Jun 15, 2019 at 02:16:11AM +0800, Gao Xiang wrote:
> >> At last, this is RFC patch v1, which means it is not suitable for
> >> merging soon... I'm still working on it, testing its stability
> >> these days and hope these patches get merged for 5.3 LTS
> >> (if 5.3 is a LTS version).
> >
> > Why would 5.3 be a LTS kernel?
> >
> > curious as to how you came up with that :)
>
> My personal thought is about one LTS kernel one year...
> Usually 5 versions after the previous kernel...(4.4 -> 4.9 -> 4.14 -> 4.19),
> which is not suitable for all historical LTSs...just prepare for 5.3...
I try to pick the "last" kernel that is released each year, which
sometimes is 5 kernels, sometimes 4, sometimes 6, depending on the
release cycle.
So odds are it will be 5.4 for the next LTS kernel, but we will not know
more until it gets closer to release time.
thanks,
greg k-h
Powered by blists - more mailing lists