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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 28 Nov 2009 02:19:09 -0800
From:	Brian Swetland <swetland@...gle.com>
To:	Corentin Chary <corentincj@...aif.net>,
	Arve Hjønnevåg <arve@...gle.com>
Cc:	Greg Kroah-Hartman <greg@...ah.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 12:45 AM, Corentin Chary <corentincj@...aif.net> 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 ?
>
> Is there any chance that all android stuff would be merged one day ?
> Actually, we got a working 2.6.32 kernel for android here (with wakelock, ashm, etc..):
> http://git.iksaif.net/?p=android-x86/kernel;a=shortlog;h=refs/heads/android-x86-backport

Arve's done a few revisions of the wakelock code with the linux-pm
list, and I know he's planning on trying to work through the remaining
issues (as I recall there was some discussion on read/write vs ioctl
interfaces to userspace) in the near future.

This really is the one piece that has the most impact on everything
else -- maintaining versions of the various platform hardware drivers
with and without wakelock support is messy.

I'm not sure if there are seriously issues with picking up ashmem or
logger.  They are relatively small, simple, and self-contained.  The
binder driver seemed to be much more contentious.

Brian
--
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/