From: Greg KH <gregkh@suse.de>
To: David Rientjes <rientjes@google.com>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
sfr@canb.auug.org.au, Andrew Morton <akpm@linux-foundation.org>,
Arve Hjonnevag <arve@android.com>, San Mehat <san@android.com>
Subject: Re: [PATCH] linux-next: 20090929 - android driver build breaks
Date: Thu, 8 Oct 2009 17:22:30 -0700 [thread overview]
Message-ID: <20091009002230.GB28982@suse.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0910081644200.14247@chino.kir.corp.google.com>
On Thu, Oct 08, 2009 at 04:48:23PM -0700, David Rientjes wrote:
> On Thu, 8 Oct 2009, Greg KH wrote:
>
> > > What are you specifically referring to? Kamalesh provided a patch[*] that
> > > fixes this particular compile error, which you said you were queueing.
> >
> > Hm, I did say I was queueing it, but I still can't figure out if this is
> > needed for the 2.6.32 tree. Is it?
> >
>
> Yes, 28b83c5 was merged during the merge window for 2.6.32 so this needs
> to be pushed for the staging tree if it's not ripped out.
Ok, I'll dig it up, thanks.
> > > If it's a criticism of the staleness of the Android code within the
> > > staging tree or no recent activity, then we should probably loop in some
> > > Android developers to find our about their plans. I've added them to the
> > > cc.
> >
> > They know all about this and agreed that the code should be dropped for
> > 2.6.33 if no one sends me patches. If someone does, then I will remove
> > my 'delete the android code' patch in the staging tree.
> >
>
> I don't work with Android, but the "no support from Google" phrase caught
> my attention :) It seems like this isn't necessarily about support or
> raised issues not being addressed, but rather about a lack of progress
> being made developmentally or a general lack of interest in upstream
> inclusion.
Yes, that is exactly correct.
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-09 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 4:04 linux-next: Tree for September 29 Stephen Rothwell
2009-09-29 15:20 ` [PATCH] linux-next: 20090929 - android driver build breaks Kamalesh Babulal
2009-09-29 15:33 ` Greg KH
2009-10-08 22:47 ` Greg KH
2009-10-08 23:24 ` David Rientjes
2009-10-08 23:28 ` Greg KH
2009-10-08 23:48 ` David Rientjes
2009-10-09 0:22 ` Greg KH [this message]
2009-10-11 9:05 ` Pavel Machek
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=20091009002230.GB28982@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rientjes@google.com \
--cc=san@android.com \
--cc=sfr@canb.auug.org.au \
/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.