From: Minchan Kim <minchan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Jens Axboe <axboe@kernel.dk>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
gaowanlong@cn.fujitsu.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] zram/zsmalloc promotion
Date: Thu, 1 Nov 2012 11:45:36 +0900 [thread overview]
Message-ID: <20121101024536.GC24883@bbox> (raw)
In-Reply-To: <20121031161900.GG31804@kroah.com>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-11-01 2:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 8:56 [PATCH v3 0/3] zram/zsmalloc promotion Minchan Kim
2012-10-29 8:56 ` [PATCH v3 1/3] zsmalloc: promote to lib/ Minchan Kim
2012-10-29 8:56 ` [PATCH v3 2/3] zram: promote zram from staging Minchan Kim
2012-10-29 8:56 ` [PATCH v3 3/3] zram: select ZSMALLOC when ZRAM is configured Minchan Kim
2012-10-29 15:43 ` [PATCH v3 0/3] zram/zsmalloc promotion Seth Jennings
2012-10-31 1:06 ` Minchan Kim
2012-10-31 1:42 ` Greg Kroah-Hartman
2012-10-31 2:04 ` Minchan Kim
2012-10-31 2:16 ` Greg Kroah-Hartman
2012-10-31 2:39 ` Minchan Kim
2012-10-31 2:43 ` Greg Kroah-Hartman
2012-10-31 7:02 ` Minchan Kim
2012-10-31 16:19 ` Greg Kroah-Hartman
2012-11-01 2:45 ` Minchan Kim [this message]
[not found] <<1351501009-15111-1-git-send-email-minchan@kernel.org>
2012-10-29 15:25 ` Dan Magenheimer
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=20121101024536.GC24883@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dan.magenheimer@oracle.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
--cc=sjenning@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).