From: Pekka Enberg <penberg@kernel.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Nitin Gupta <ngupta@vflare.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Jens Axboe <axboe@kernel.dk>,
gaowanlong@cn.fujitsu.com
Subject: Re: [PATCH v4 3/3] zram: select ZSMALLOC when ZRAM is configured
Date: Fri, 2 Nov 2012 10:23:21 +0200 [thread overview]
Message-ID: <CAOJsxLFfH4R+mVtCgQB2xpRPBZerZLKLq5UNM0k2+2U5YyzRPw@mail.gmail.com> (raw)
In-Reply-To: <1351840367-4152-4-git-send-email-minchan@kernel.org>
On Fri, Nov 2, 2012 at 9:12 AM, Minchan Kim <minchan@kernel.org> wrote:
> At the monent, we can configure zram in driver/block once zsmalloc
> in /lib menu is configured firstly. It's not convenient.
>
> User can configure zram in driver/block regardless of zsmalloc enabling
> by this patch.
>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
Acked-by: Pekka Enberg <penberg@kernel.org>
--
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-02 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 7:12 [PATCH v4 0/3] zram/zsmalloc promotion Minchan Kim
2012-11-02 7:12 ` [PATCH v4 1/3] zsmalloc: promote to lib/ Minchan Kim
2012-11-02 8:22 ` Pekka Enberg
2012-11-02 7:12 ` [PATCH v4 2/3] zram: promote zram from staging Minchan Kim
2012-11-02 7:12 ` [PATCH v4 3/3] zram: select ZSMALLOC when ZRAM is configured Minchan Kim
2012-11-02 8:23 ` Pekka Enberg [this message]
2012-11-06 23:32 ` [PATCH v4 0/3] zram/zsmalloc promotion Andrew Morton
[not found] ` <CAEwNFnAA+PNh0OT7vdv5k5u3TXeBUDJZX75TQg_Si4yFnE6e-g@mail.gmail.com>
2012-11-07 10:38 ` Minchan Kim
2012-11-07 16:40 ` Luigi Semenzato
2012-11-19 1:27 ` Minchan Kim
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=CAOJsxLFfH4R+mVtCgQB2xpRPBZerZLKLq5UNM0k2+2U5YyzRPw@mail.gmail.com \
--to=penberg@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=minchan@kernel.org \
--cc=ngupta@vflare.org \
--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