linux-kernel - Re: [PATCH 1/4] Support generic I/O requests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C0609F2.10802@vflare.org>
Date:	Wed, 02 Jun 2010 13:06:18 +0530
From:	Nitin Gupta <ngupta@...are.org>
To:	Minchan Kim <minchan.kim@...il.com>
CC:	Greg KH <greg@...ah.com>, Pekka Enberg <penberg@...helsinki.fi>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ed Tomlinson <edt@....ca>,
	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	Cyp <cyp561@...il.com>, driverdev <devel@...verdev.osuosl.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] Support generic I/O requests

On 06/02/2010 11:50 AM, Minchan Kim wrote:
> On Tue, Jun 1, 2010 at 5:01 PM, Nitin Gupta <ngupta@...are.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
--
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/