From: Alex Courbot <acourbot@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (gpio tree related)
Date: Wed, 30 Oct 2013 09:56:19 +0900 [thread overview]
Message-ID: <52705933.3060304@nvidia.com> (raw)
In-Reply-To: <CACRpkdZ444P-zWx99T2+=nEO13Gbub2rYpE91eW0UoRFc4kdSg@mail.gmail.com>
On 10/29/2013 10:25 PM, Linus Walleij wrote:
> On Tue, Oct 29, 2013 at 10:10 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>> I have applied the following patch for today (it should go into the gpio
>> tree if it is considered correct):
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Tue, 29 Oct 2013 20:05:12 +1100
>> Subject: [PATCH] gpiolib: include gpio/consumer.h in of_gpio.h for
>> desc_to_gpio()
>>
>> Fixes this build error on sparc:
>>
>> In file included from drivers/spi/spi.c:33:0:
>> include/linux/of_gpio.h: In function 'of_get_named_gpio_flags':
>> include/linux/of_gpio.h:93:3: error: implicit declaration of function 'desc_to_gpio' [-Werror=implicit-function-declaration]
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> Patch applied, unless Alexandre has any considerations.
Nope, that include should definitely be there, actually I was convinced
it was already...
Alex.
next prev parent reply other threads:[~2013-10-30 0:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 9:10 linux-next: build failure after merge of the final tree (gpio tree related) Stephen Rothwell
2013-10-29 13:25 ` Linus Walleij
2013-10-30 0:56 ` Alex Courbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 6:35 Stephen Rothwell
2014-03-05 7:16 ` Linus Walleij
2014-03-05 16:42 ` Fabian Vogt
2013-12-23 4:54 Stephen Rothwell
2013-10-28 14:12 Stephen Rothwell
2013-10-29 13:28 ` Linus Walleij
2012-02-06 4:23 Stephen Rothwell
2012-02-06 6:07 ` Grant Likely
2012-02-06 14:02 ` Mark Brown
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=52705933.3060304@nvidia.com \
--to=acourbot@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.