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: Tue, 31 Aug 2010 02:03:44 -0600 [thread overview]
Message-ID: <20100831080344.GA20515@angua.secretlab.ca> (raw)
In-Reply-To: <20100824092623.GA20334@oksana.dev.rtsoft.ru>
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.
g.
> ---
>
> On Tue, Aug 24, 2010 at 04:26:08PM +1000, Benjamin Herrenschmidt wrote:
> > I get that with my current stuff:
> >
> > cc1: warnings being treated as errors
> > In file included from [..]/mpc52xx_common.c:19:
> > of_gpio.h:74: error: ‘struct gpio_chip’ declared inside parameter list
> [...]
> > make[3]: *** Waiting for unfinished jobs....
>
> That's because with GPIOCHIP=n no one declares struct gpio_chip.
>
> It should be either of_gpio.h or gpio.h. Let's make it gpio.h, as
> this feels more generic, and we already have some !GPIOLIB handling
> in there.
>
> include/linux/gpio.h | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/gpio.h b/include/linux/gpio.h
> index 03f616b..85207d2 100644
> --- a/include/linux/gpio.h
> +++ b/include/linux/gpio.h
> @@ -15,6 +15,12 @@
> struct device;
>
> /*
> + * Some code might rely on the declaration. Still, it is illegal
> + * to dereference it for !GPIOLIB case.
> + */
> +struct gpio_chip;
> +
> +/*
> * Some platforms don't support the GPIO programming interface.
> *
> * In case some driver uses it anyway (it should normally have
> --
> 1.7.0.5
>
next prev parent reply other threads:[~2010-08-31 8:03 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 [this message]
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
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=20100831080344.GA20515@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).