linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Dream in staging: separate Kconfig/Makefile into subdirectory
Date: Wed, 5 Aug 2009 09:06:52 -0700	[thread overview]
Message-ID: <20090805160652.GA9474@kroah.com> (raw)
In-Reply-To: <20090805152721.GA8337@elf.ucw.cz>

On Wed, Aug 05, 2009 at 05:27:21PM +0200, Pavel Machek wrote:
> On Mon 2009-07-27 08:37:11, Greg KH wrote:
> > On Mon, Jul 20, 2009 at 12:35:32PM +0200, Pavel Machek wrote:
> > > Separate Kconfig/Makefile glue from dream into subdirectory. I plan to
> > > add few more drivers, and changing staging/Makefile each time sounds
> > > like inviting conflicts.
> > >     
> > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > > 
> > > diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig
> > > index 300b83e..50f9ab0 100644
> > > --- a/drivers/staging/Kconfig
> > > +++ b/drivers/staging/Kconfig
> > > @@ -133,11 +133,9 @@ source "drivers/staging/cpc-usb/Kconfig"
> > >  
> > >  source "drivers/staging/pata_rdc/Kconfig"
> > >  
> > > -source "drivers/staging/dream/smd/Kconfig"
> > > -
> > > -source "drivers/staging/dream/camera/Kconfig"
> > > -
> > >  source "drivers/staging/udlfb/Kconfig"
> > >  
> > > +source "drivers/staging/dream/Kconfig"
> > > +
> > >  endif # !STAGING_EXCLUDE_BUILD
> > >  endif # STAGING
> > > diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile
> > > index 8d2e1c2..4fa2e07 100644
> > > --- a/drivers/staging/Makefile
> > > +++ b/drivers/staging/Makefile
> > > @@ -1,7 +1,7 @@
> > >  # Makefile for staging directory
> > >  
> > >  # fix for build system bug...
> > > -obj-$(CONFIG_STAGING)		+= staging.o
> > > +obj-$(CONFIG_STAGING)		+= staging.o dream/
> > 
> > Ick, no, you shouldn't have to do this.
> > 
> > Please jump into the dream subdir based on a Kconfig option, don't go
> > there every single time.
> > 
> > Care to fix this up?
> 
> I'm afraid I don't quite have suitable config option. At least
> synaptics touchpad should be usable outside dream.
> 
> OTOH Dream is still major user; and I guess I can just introduce
> "CONFIG_DREAM". Should I?

What's wrong with using the CONFIG_ANDROID dependancy here?  Actually,
why not use it for all of the dream files?

Or yes, you can create CONFIG_DREAM if you want, but there's probably a
better, arch-specific config item that you want to use.

thanks,

greg k-h

  reply	other threads:[~2009-08-05 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 10:35 Dream in staging: separate Kconfig/Makefile into subdirectory Pavel Machek
2009-07-21 12:16 ` Bartlomiej Zolnierkiewicz
2009-07-21 10:38   ` Pavel Machek
2009-07-27 15:37 ` Greg KH
2009-08-05 15:27   ` Pavel Machek
2009-08-05 16:06     ` Greg KH [this message]
2009-08-05 23:01       ` Pavel Machek
2009-08-08 12:27       ` Pavel Machek
2009-08-17 20:36         ` patch staging-dream-separate-kconfig-makefile-into-subdirectory.patch added to gregkh-2.6 tree gregkh
2009-08-17 21:23         ` gregkh

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=20090805160652.GA9474@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).