From: Grant Likely <grant.likely@secretlab.ca>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: David Brownell <david-b@pacbell.net>,
Andrew Morton <akpm@linux-foundation.org>,
Benjamin Herrenschmidt <benh@au1.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: Add 'struct gpio_chip' forward declaration for !GPIOLIB case
Date: Wed, 1 Sep 2010 09:26:16 -0600 [thread overview]
Message-ID: <20100901152616.GD13421@angua.secretlab.ca> (raw)
In-Reply-To: <20100831170756.GA24887@oksana.dev.rtsoft.ru>
On Tue, Aug 31, 2010 at 09:07:56PM +0400, Anton Vorontsov wrote:
> On Tue, Aug 31, 2010 at 10:44:14AM -0600, Grant Likely wrote:
> > On Tue, Aug 31, 2010 at 2:37 AM, Anton Vorontsov <cbouatmailru@gmail.com> wrote:
> > > On Tue, Aug 31, 2010 at 02:03:44AM -0600, Grant Likely wrote:
> > >> On Tue, Aug 24, 2010 at 01:26:23PM +0400, Anton Vorontsov wrote:
> > >> > With CONFIG_GPIOLIB=n, the 'struct gpio_chip' is not declared,
> > >> > so the following pops up on PowerPC:
> > >> >
> > >> > cc1: warnings being treated as errors
> > >> > In file included from arch/powerpc/platforms/52xx/mpc52xx_common.c:19:
> > >> > include/linux/of_gpio.h:74: warning: 'struct gpio_chip' declared
> > >> > inside parameter list
> > >> > include/linux/of_gpio.h:74: warning: its scope is only this definition
> > >> > or declaration, which is probably not what
> > >> > you want
> > >> > include/linux/of_gpio.h:75: warning: 'struct gpio_chip' declared
> > >> > inside parameter list
> > >> > make[2]: *** [arch/powerpc/platforms/52xx/mpc52xx_common.o] Error 1
> > >> >
> > >> > This patch fixes the issue by providing the proper forward declaration.
> > >> >
> > >> > Signed-off-by: Anton Vorontsov <cbouatmailru@gmail.com>
> > >>
> > >> This doesn't actually solve the problem, and gpiochip should
> > >> remain undefined when CONFIG_GPIOLIB=n to catch exactly these
> > >> build failures. The real problem is that I merged a change
> > >> into the mpc5200 code that required CONFIG_GPIOLIB be enabled
> > >> without reflecting that requirement in Kconfig.
> > >
> > > No, look closer. The error is in of_gpio.h, and it's perfectly
> > > fine to include it w/o GPIOLIB=y.
> >
> > Looking even closer, we're both wrong. You're right I didn't look
> > carefully enough, and the error is in of_gpio.h, not the .c file.
> >
> > However, it is not okay to get the definitions from of_gpio.h when
> > CONFIG_GPIOLIB=n. If GPIOLIB, or more specifically OF_GPIO isn't set,
> > then the of_gpio.h definitions should either not be defined, or should
> > be defined as empty stubs (where appropriate).
>
> Grrr. Grant, look again, even closer than you did.
Gah. Very bad day yesterday. Applied and sorry for the noise.
g.
prev parent reply other threads:[~2010-09-01 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 6:26 52xx build error Benjamin Herrenschmidt
2010-08-24 9:26 ` [PATCH] gpiolib: Add 'struct gpio_chip' forward declaration for !GPIOLIB case Anton Vorontsov
2010-08-31 8:03 ` Grant Likely
2010-08-31 8:37 ` Anton Vorontsov
2010-08-31 16:44 ` Grant Likely
2010-08-31 17:07 ` Anton Vorontsov
2010-09-01 15:26 ` Grant Likely [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=20100901152616.GD13421@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=benh@au1.ibm.com \
--cc=cbouatmailru@gmail.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).