linux-kernel - Re: [PATCH 0/2] staging/android fixes

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 28 Nov 2009 10:58:46 -0800
From:	Greg KH <greg@...ah.com>
To:	Corentin Chary <corentincj@...aif.net>
Cc:	Brian Swetland <swetland@...gle.com>,
	Chih-Wei Huang <cwhuang@...ux.org.tw>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] staging/android fixes

On Sat, Nov 28, 2009 at 09:45:13AM +0100, Corentin Chary wrote:
> Hi,
> Here is a patch to fix build for android specifics drivers.
> 
> What we should do next to prevent them from being removed in 2.6.23 ?

Provide _real_ forward progress on the code.  Google has not contributed
anything, and neither has anyone else, becides various tiny fixups, like
the low-memory one that you just did.

> Is there any chance that all android stuff would be merged one day ?

That is up to the developers of the code.  I would hope that it would,
but it needs a _lot_ of work to get there.

So for now, unless you are willing to maintain this code and work to get
it merged into the main kernel tree (which will require changes to the
kernel/userspace apis in a number of places, which will require buy-in
by the owners of that userspace code), I'm going to have to drop the
code.

sorry,

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/