From: Greg KH <greg@kroah.com>
To: Corentin Chary <corentincj@iksaif.net>
Cc: Brian Swetland <swetland@google.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 10:58:46 -0800 [thread overview]
Message-ID: <20091128185846.GA23662@kroah.com> (raw)
In-Reply-To: <1259397915-762-1-git-send-email-corentincj@iksaif.net>
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
prev parent reply other threads:[~2009-11-28 19:11 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
2009-11-29 9:38 ` Brian Swetland
2009-11-30 12:30 ` Pavel Machek
2009-11-28 18:58 ` Greg KH [this message]
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=20091128185846.GA23662@kroah.com \
--to=greg@kroah.com \
--cc=corentincj@iksaif.net \
--cc=cwhuang@linux.org.tw \
--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.