From: Nitin Gupta <ngupta@vflare.org>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Greg KH <greg@kroah.com>, Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
Ed Tomlinson <edt@aei.ca>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>, Cyp <cyp561@gmail.com>,
driverdev <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] Support generic I/O requests
Date: Wed, 02 Jun 2010 13:06:18 +0530 [thread overview]
Message-ID: <4C0609F2.10802@vflare.org> (raw)
In-Reply-To: <AANLkTimjc8eZY2IqbeZUR7VsWVspZ4ilUz3LPAUIiZuU@mail.gmail.com>
On 06/02/2010 11:50 AM, Minchan Kim wrote:
> On Tue, Jun 1, 2010 at 5:01 PM, Nitin Gupta <ngupta@vflare.org> wrote:
> P.S)
> Why don't you send this series to -mm?
In general, zram is somewhat related to memory management but these zram
patches mainly deal with handling generic I/O requests. So, I just posted
them on linux-kernel. Even if changes were made to xvmalloc, I doubt
if anyone at -mm would be interested in a driver specific allocator.
> I don't know any patches have to go linux-next and any patches have to
> go --mmotm.
> I thought zram is related to memory management a little bit.
>
> What's the criteria?
>
I *guess* anything experimental goes to linux-next and if thats related
directly to core mm, it goes to --mmotm also.
Thanks,
Nitin
next prev parent reply other threads:[~2010-06-02 7:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 8:01 [PATCH 0/4] zram: generic RAM based compressed R/W block devices (v2) Nitin Gupta
2010-06-01 8:01 ` [PATCH 1/4] Support generic I/O requests Nitin Gupta
2010-06-02 6:20 ` Minchan Kim
2010-06-02 7:36 ` Nitin Gupta [this message]
2010-06-04 19:19 ` Andrew Morton
2010-06-05 8:28 ` Pekka Enberg
2010-06-05 8:36 ` Pekka Enberg
2010-06-05 8:35 ` Pekka Enberg
2010-06-05 13:15 ` Nitin Gupta
2010-06-06 23:32 ` Minchan Kim
2010-06-07 5:35 ` Pekka Enberg
2010-06-04 19:10 ` Andrew Morton
2010-06-05 7:44 ` Nitin Gupta
2010-06-01 8:01 ` [PATCH 2/4] Rename ramzswap files to zram Nitin Gupta
2010-06-04 19:32 ` Andrew Morton
2010-06-04 21:07 ` Greg KH
2010-06-05 7:00 ` Nitin Gupta
2010-06-01 8:01 ` [PATCH 3/4] Rename ramzswap to zram in code Nitin Gupta
2010-06-01 8:01 ` [PATCH 4/4] Rename ramzswap to zram in documentation Nitin Gupta
2010-06-01 10:25 ` [PATCH 0/4] zram: generic RAM based compressed R/W block devices (v2) Pekka Enberg
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=4C0609F2.10802@vflare.org \
--to=ngupta@vflare.org \
--cc=akpm@linux-foundation.org \
--cc=cyp561@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=edt@aei.ca \
--cc=greg@kroah.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan.kim@gmail.com \
--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.