From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
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: Mon, 29 Oct 2012 10:43:19 -0500 [thread overview]
Message-ID: <508EA417.1040304@linux.vnet.ibm.com> (raw)
In-Reply-To: <1351501009-15111-1-git-send-email-minchan@kernel.org>
On 10/29/2012 03:56 AM, Minchan Kim wrote:
> This patchset promotes zram/zsmalloc from staging.
> Both are very clean and zram have been used by many embedded product
> for a long time.
> It's time to go out of staging.
Agreed!
> Greg, Jens is already OK that zram is located under driver/blocks/.
> The issue remained is where we put zsmalloc.
Doesn't matter much for me, but seems to be leaning toward /lib,
baring an opinion from Andrew that it go in /mm. /lib is fine by me.
Seth
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
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: Mon, 29 Oct 2012 10:43:19 -0500 [thread overview]
Message-ID: <508EA417.1040304@linux.vnet.ibm.com> (raw)
In-Reply-To: <1351501009-15111-1-git-send-email-minchan@kernel.org>
On 10/29/2012 03:56 AM, Minchan Kim wrote:
> This patchset promotes zram/zsmalloc from staging.
> Both are very clean and zram have been used by many embedded product
> for a long time.
> It's time to go out of staging.
Agreed!
> Greg, Jens is already OK that zram is located under driver/blocks/.
> The issue remained is where we put zsmalloc.
Doesn't matter much for me, but seems to be leaning toward /lib,
baring an opinion from Andrew that it go in /mm. /lib is fine by me.
Seth
next prev parent reply other threads:[~2012-10-29 15:43 UTC|newest]
Thread overview: 30+ 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 ` Minchan Kim
2012-10-29 8:56 ` [PATCH v3 1/3] zsmalloc: promote to lib/ Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 8:56 ` [PATCH v3 2/3] zram: promote zram from staging Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 8:56 ` [PATCH v3 3/3] zram: select ZSMALLOC when ZRAM is configured Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 15:43 ` Seth Jennings [this message]
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:06 ` Minchan Kim
2012-10-31 1:42 ` Greg Kroah-Hartman
2012-10-31 1:42 ` Greg Kroah-Hartman
2012-10-31 2:04 ` Minchan Kim
2012-10-31 2:04 ` Minchan Kim
2012-10-31 2:16 ` Greg Kroah-Hartman
2012-10-31 2:16 ` Greg Kroah-Hartman
2012-10-31 2:39 ` Minchan Kim
2012-10-31 2:39 ` Minchan Kim
2012-10-31 2:43 ` Greg Kroah-Hartman
2012-10-31 2:43 ` Greg Kroah-Hartman
2012-10-31 7:02 ` Minchan Kim
2012-10-31 7:02 ` Minchan Kim
2012-10-31 16:19 ` Greg Kroah-Hartman
2012-10-31 16:19 ` Greg Kroah-Hartman
2012-11-01 2:45 ` Minchan Kim
2012-11-01 2:45 ` Minchan Kim
[not found] <<1351501009-15111-1-git-send-email-minchan@kernel.org>
2012-10-29 15:25 ` Dan Magenheimer
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=508EA417.1040304@linux.vnet.ibm.com \
--to=sjenning@linux.vnet.ibm.com \
--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=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
/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.