From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Shiraz Hashim <shiraz.hashim@st.com>
Subject: Re: linux-next: build failure after merge of the final tree (pinctrl tree related)
Date: Thu, 8 Nov 2012 14:06:37 +0100 [thread overview]
Message-ID: <CACRpkdb4LVG8TG58DmUMHRL3r0r4hn7wh-y47metBwth5c52-A@mail.gmail.com> (raw)
In-Reply-To: <20121107154837.05c74508452d69930b624280@canb.auug.org.au>
On Wed, Nov 7, 2012 at 5:48 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Caused by commit e8321df59155 ("gpiolib: iron out include ladder
> mistakes") (and some earlier ones) from the pinctrl tree.
>
> I added this patch for today (there may be a better return value from
> gpiochip_add_pin_range):
(..)
> +struct gpio_chip;
> +
> static inline int
> gpiochip_add_pin_range(struct gpio_chip *chip, const char *pinctl_name,
> unsigned int pin_base, unsigned int npins)
> {
> + return 0;
> }
Bah, I happened to put these prototypes just above the actual definition
of struct gpio_chip :-P
Fixing up and respinning the patch, I've added the compulsory return
value as well.
Yours,
Linus Walleij
prev parent reply other threads:[~2012-11-08 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 4:48 linux-next: build failure after merge of the final tree (pinctrl tree related) Stephen Rothwell
2012-11-08 13:06 ` Linus Walleij [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=CACRpkdb4LVG8TG58DmUMHRL3r0r4hn7wh-y47metBwth5c52-A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shiraz.hashim@st.com \
/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).