From: Pavel Machek <pavel@ucw.cz>
To: Brian Swetland <swetland@google.com>
Cc: Corentin Chary <corentincj@iksaif.net>,
Arve Hj??nnev??g <arve@google.com>,
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: Sun, 29 Nov 2009 09:43:52 +0100 [thread overview]
Message-ID: <20091129084351.GD1530@ucw.cz> (raw)
In-Reply-To: <a55d774e0911280219s69729b54l544660aac4b2197@mail.gmail.com>
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.
It is really not that bad. Yes, it touches most drivers, but it is few
lines per driver and easy to remove.
Waiting for wakelocks (1year plus, AFAICT) before merging hw drivers
seems like very slow way forward.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-11-29 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 8:45 [PATCH 0/2] staging/android fixes 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 ` [PATCH 0/2] staging/android fixes Brian Swetland
2009-11-29 8:43 ` Pavel Machek [this message]
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=20091129084351.GD1530@ucw.cz \
--to=pavel@ucw.cz \
--cc=arve@google.com \
--cc=corentincj@iksaif.net \
--cc=cwhuang@linux.org.tw \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.