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: <20120319233409.GA16124@kroah.com>
Date:	Mon, 19 Mar 2012 16:34:09 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Seth Jennings <sjenning@...ux.vnet.ibm.com>
Cc:	devel@...verdev.osuosl.org,
	Dan Magenheimer <dan.magenheimer@...cle.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Robert Jennings <rcj@...ux.vnet.ibm.com>,
	Nitin Gupta <ngupta@...are.org>
Subject: Re: [PATCH] staging: zsmalloc: add user-definable alloc/free funcs

On Mon, Mar 19, 2012 at 01:54:56PM -0500, Seth Jennings wrote:
> > I'm sorry, I know this isn't fair for your specific patch, but we have
> > to stop this sometime, and as this patch adds code isn't even used by
> > anyone, its a good of a time as any.
> 
> So, this the my first "promotion from staging" rodeo.  I would love to
> see this code mainlined ASAP.  How would I/we go about doing that?

What subsystem should this code live in?  The -mm code, I'm guessing,
right?  If so, submit it to the linux-mm mailing list for inclusion, you
can point them at what is in drivers/staging right now, or probably it's
easier if you just make a new patch that adds the code that is in
drivers/staging/ to the correct location in the kernel.  That way it's
easier to review and change.  When it finally gets accepted, we can then
delete the drivers/staging code.

hope this helps,

greg k-h
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ