All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Daniel Drake <dsd@laptop.org>,
	Jens Frederich <jfrederich@gmail.com>,
	Jon Nettleton <jon.nettleton@gmail.com>
Subject: Re: [PATCH v2] staging/olpc_dcon: fix kconfig to fix build errors
Date: Tue, 15 Oct 2013 12:24:29 -0700	[thread overview]
Message-ID: <20131015192429.GA6063@kroah.com> (raw)
In-Reply-To: <525C6F9F.3030801@infradead.org>

On Mon, Oct 14, 2013 at 03:26:39PM -0700, Randy Dunlap wrote:
> On 10/14/13 09:33, Greg Kroah-Hartman wrote:
> > On Sun, Oct 13, 2013 at 12:30:00PM -0700, Randy Dunlap wrote:
> >> From: Randy Dunlap <rdunlap@infradead.org>
> >>
> >> Fix build errors when GPIO_CS5535=m and FB_OLPC_DCON=y
> >> by preventing that kconfig combination.
> >>
> >> These build errors are caused by having a kconfig bool symbol
> >> (FB_OLPC_DCON_1) that depend on a tristate symbol (GPIO_CS5535),
> >> but when the tristate symbol is =m, the bool symbol is =y.
> >>
> >>   drivers/built-in.o: In function `dcon_read_status_xo_1':
> >>   olpc_dcon_xo_1.c:(.text+0x359531): undefined reference to `cs5535_gpio_set'
> >>   drivers/built-in.o: In function `dcon_wiggle_xo_1':
> >>   olpc_dcon_xo_1.c:(.text+0x35959f): undefined reference to `cs5535_gpio_set'
> >>   olpc_dcon_xo_1.c:(.text+0x359610): undefined reference to `cs5535_gpio_clear'
> >>   drivers/built-in.o:olpc_dcon_xo_1.c:(.text+0x3596a1): more undefined references to `cs5535_gpio_clear' follow
> >>   drivers/built-in.o: In function `dcon_wiggle_xo_1':
> >>   olpc_dcon_xo_1.c:(.text+0x359708): undefined reference to `cs5535_gpio_set'
> >>   drivers/built-in.o: In function `dcon_init_xo_1':
> >>   olpc_dcon_xo_1.c:(.text+0x35989b): undefined reference to `cs5535_gpio_clear'
> >>   olpc_dcon_xo_1.c:(.text+0x3598b5): undefined reference to `cs5535_gpio_isset'
> >>   olpc_dcon_xo_1.c:(.text+0x359963): undefined reference to `cs5535_gpio_setup_event'
> >>   olpc_dcon_xo_1.c:(.text+0x359980): undefined reference to `cs5535_gpio_set_irq'
> >>   olpc_dcon_xo_1.c:(.text+0x359a36): undefined reference to `cs5535_gpio_set'
> >>
> >> However, adding GPIO_CS5535 to the Kconfig dependencies also creates
> >> a kconfig recursive dependency error on powerpc:
> >>   drivers/i2c/Kconfig:5:error: recursive dependency detected!
> >>   drivers/i2c/Kconfig:5:	symbol I2C is selected by FB_OLPC_DCON
> >>   drivers/staging/olpc_dcon/Kconfig:1:	symbol FB_OLPC_DCON depends on GPIO_CS5535
> >>   drivers/gpio/Kconfig:577:	symbol GPIO_CS5535 depends on GPIOLIB
> >>   drivers/gpio/Kconfig:38:	symbol GPIOLIB is selected by ARCH_REQUIRE_GPIOLIB
> >>   drivers/gpio/Kconfig:23:	symbol ARCH_REQUIRE_GPIOLIB is selected by MCU_MPC8349EMITX
> >>   arch/powerpc/platforms/Kconfig:351:	symbol MCU_MPC8349EMITX depends on I2C
> >>
> >> This is due to FB_OLPC_DCON selecting I2C instead of depending on it,
> >> so change the select to a dependency.
> >>
> >> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> >> Cc:	Daniel Drake <dsd@laptop.org>
> >> Cc:	Jens Frederich <jfrederich@gmail.com>
> >> Cc:	Jon Nettleton <jon.nettleton@gmail.com>
> >> ---
> >>  drivers/staging/olpc_dcon/Kconfig |    3 ++-
> >>  1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> --- lnx-312-rc4.orig/drivers/staging/olpc_dcon/Kconfig
> >> +++ lnx-312-rc4/drivers/staging/olpc_dcon/Kconfig
> >> @@ -1,7 +1,8 @@
> >>  config FB_OLPC_DCON
> >>  	tristate "One Laptop Per Child Display CONtroller support"
> >>  	depends on OLPC && FB
> >> -	select I2C
> >> +	depends on I2C
> >> +	depends on (GPIO_CS5535 || GPIO_CS5535=n)
> > 
> > 
> > This fails to apply to my staging-next branch of staging.git due to a
> > previous patch from you to try to fix this same issue (or maybe a
> > different one, I don't know...)
> 
> 
> You had asked if the previous patch should be reverted and I replied (very
> belatedly) Yes.  However, I'll be glad to make a new patch against
> linux-next instead of mainline.

Ah, missed that, I've now reverted it and will apply this one instead.

thanks,

greg k-h

      reply	other threads:[~2013-10-15 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <524a3b76.oejnG6gfqBFdWbl/%fengguang.wu@intel.com>
2013-10-13 19:30 ` [PATCH v2] staging/olpc_dcon: fix kconfig to fix build errors Randy Dunlap
2013-10-14 16:33   ` Greg Kroah-Hartman
2013-10-14 22:26     ` Randy Dunlap
2013-10-15 19:24       ` Greg Kroah-Hartman [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=20131015192429.GA6063@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dsd@laptop.org \
    --cc=fengguang.wu@intel.com \
    --cc=jfrederich@gmail.com \
    --cc=jon.nettleton@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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.