linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@suse.de>
Cc: David Rientjes <rientjes@google.com>, Greg KH <greg@kroah.com>,
	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: Sun, 11 Oct 2009 11:05:08 +0200	[thread overview]
Message-ID: <20091011090508.GC1414@ucw.cz> (raw)
In-Reply-To: <20091008232825.GA540@suse.de>


> > 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.
> 
> Honestly, I'm not holding my breath :(

Heh, I'm glad, I did not make dream suppport dependend on
CONFIG_ANDROID... :-).

Oops, no, it does depend on it. 

Something like this?
									Pavel
---

Make Dream support idenependend of CONFIG_ANDROID.

Signed-off-by: Pavel Machek <pavel@ucw.cz>

--- linux-rc/drivers/staging.ofic/Makefile	2009-10-06 13:51:49.000000000 +0200
+++ linux-rc/drivers/staging/Makefile	2009-10-10 14:52:36.000000000 +0200
@@ -27,7 +27,7 @@
 obj-$(CONFIG_INPUT_MIMIO)	+= mimio/
 obj-$(CONFIG_TRANZPORT)		+= frontier/
 obj-$(CONFIG_ANDROID)		+= android/
-obj-$(CONFIG_ANDROID)		+= dream/
+obj-$(CONFIG_DREAM)		+= dream/
 obj-$(CONFIG_DST)		+= dst/
 obj-$(CONFIG_POHMELFS)		+= pohmelfs/
 obj-$(CONFIG_STLC45XX)		+= stlc45xx/
--- linux-rc/drivers/staging.ofic/dream/Kconfig	2009-10-06 13:52:05.000000000 +0200
+++ linux-rc/drivers/staging/dream/Kconfig	2009-10-10 14:53:11.000000000 +0200
@@ -1,3 +1,6 @@
+config DREAM
+       tristate "HTC Dream support"
+
 source "drivers/staging/dream/smd/Kconfig"
 
 source "drivers/staging/dream/camera/Kconfig"



-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2009-10-11  9:05 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
2009-10-11  9:05         ` Pavel Machek [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=20091011090508.GC1414@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=arve@android.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).