From: Brian Swetland <swetland@google.com>
To: "Corentin Chary" <corentincj@iksaif.net>,
"Arve Hjønnevåg" <arve@google.com>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
Chih-Wei Huang <cwhuang@linux.org.tw>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] staging/android fixes
Date: Sat, 28 Nov 2009 02:19:09 -0800 [thread overview]
Message-ID: <a55d774e0911280219s69729b54l544660aac4b2197@mail.gmail.com> (raw)
In-Reply-To: <1259397915-762-1-git-send-email-corentincj@iksaif.net>
On Sat, Nov 28, 2009 at 12:45 AM, Corentin Chary <corentincj@iksaif.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
next prev parent reply other threads:[~2009-11-28 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 8:45 Corentin Chary
2009-11-28 8:45 ` [PATCH 1/2] staging/android: fix build issues Corentin Chary
2009-11-28 8:45 ` [PATCH 2/2] staging/android: remove BROKEN flag Corentin Chary
2009-11-28 10:19 ` Brian Swetland [this message]
2009-11-29 8:43 ` [PATCH 0/2] staging/android fixes Pavel Machek
2009-11-29 9:38 ` Brian Swetland
2009-11-30 12:30 ` Pavel Machek
2009-11-28 18:58 ` Greg KH
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=a55d774e0911280219s69729b54l544660aac4b2197@mail.gmail.com \
--to=swetland@google.com \
--cc=arve@google.com \
--cc=corentincj@iksaif.net \
--cc=cwhuang@linux.org.tw \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®