[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121101024536.GC24883@bbox>
Date: Thu, 1 Nov 2012 11:45:36 +0900
From: Minchan Kim <minchan@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Nitin Gupta <ngupta@...are.org>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Seth Jennings <sjenning@...ux.vnet.ibm.com>,
Jens Axboe <axboe@...nel.dk>,
Dan Magenheimer <dan.magenheimer@...cle.com>,
Pekka Enberg <penberg@...helsinki.fi>,
gaowanlong@...fujitsu.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH v3 0/3] zram/zsmalloc promotion
On Wed, Oct 31, 2012 at 09:19:00AM -0700, Greg Kroah-Hartman wrote:
> On Wed, Oct 31, 2012 at 04:02:02PM +0900, Minchan Kim wrote:
> > On Tue, Oct 30, 2012 at 07:43:07PM -0700, Greg Kroah-Hartman wrote:
> > > On Wed, Oct 31, 2012 at 11:39:48AM +0900, Minchan Kim wrote:
> > > > Greg, what do you think about LTSI?
> > > > Is it proper feature to add it? For it, still do I need ACK from mm developers?
> > >
> > > It's already in LTSI, as it's in the 3.4 kernel, right?
> >
> > Right. But as I look, it seems to be based on 3.4.11 which doesn't have
> > recent bug fix and enhances and current 3.4.16 also doesn't include it.
>
> You can ask for those bugfixes to get backported to the stable/longterm
> kernel tree, see Documentation/stable_kernel_rules.txt for how to do
> this properly.
>
> > Just out of curiosity.
> >
> > Is there any rule about update period in long-term kernel?
> > I mean how often you release long-term kernel.
>
> About once a week lately.
>
> > Is there any rule about update period in LTSI kernel based on long-term kernel?
>
> No, the LTSI kernel work has been slow due to the lack of time on my
> part lately.
>
> > If I get the answer on above two quesion, I can expect later what LTSI kernel
> > version include feature I need.
> >
> > Another question.
> > For example, There is A feature in mainline and A has no problem but
> > someone invents new wheel "B" which is better than A so it replace A totally
> > in recent mainline. As following stable-kernel rule, it's not a real bug fix
> > so I guess stable kernel will never replace A with B.
>
> That is correct.
>
> > It means LTSI never get a chance to use new wheel. Right?
>
> No, you can submit the same patches for the LTSI kernel as well, they
> will probably be accepted as the rules are much more "loose" for the
> LTSI tree compared to the normal stable/longterm kernel rules. Which is
> the primary reason it is around.
>
> Hope this helps,
>
> greg k-h
Thanks, Greg!
--
Kind regards,
Minchan Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists