From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Shawn Guo <shawn.guo@linaro.org>
Subject: linux-next: build failure after merge of the gpio-lw tree
Date: Fri, 18 Jan 2013 14:03:46 +1100 [thread overview]
Message-ID: <20130118140346.3f9b182aa7daa175b4f136bf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Hi Linus,
After merging the gpio-lw tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/gpio/devres.c:51:5: error: redefinition of 'devm_gpio_request'
include/linux/gpio.h:97:19: note: previous definition of 'devm_gpio_request' was here
drivers/gpio/devres.c:80:5: error: redefinition of 'devm_gpio_request_one'
include/linux/gpio.h:109:19: note: previous definition of 'devm_gpio_request_one' was here
drivers/gpio/devres.c:113:6: error: redefinition of 'devm_gpio_free'
include/linux/gpio.h:128:20: note: previous definition of 'devm_gpio_free' was here
Presumably caused by commit d39cd0301255 ("gpio: devm_gpio_* support
should not depend on GPIOLIB").
I have used the version of the gpio-lw tree from next-20130117 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-01-18 3:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 3:03 Stephen Rothwell [this message]
2013-01-18 7:57 ` [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB Shawn Guo
2013-01-18 22:33 ` Linus Walleij
2013-02-10 4:46 ` Max Filippov
2013-02-11 14:13 ` Linus Walleij
2013-02-11 16:50 ` Max Filippov
2013-02-12 12:35 ` Linus Walleij
2013-02-11 20:23 ` Stephen Rothwell
2013-02-13 13:37 ` Shawn Guo
2013-01-18 8:02 ` linux-next: build failure after merge of the gpio-lw tree Shawn Guo
2013-01-18 23:40 ` Stephen Rothwell
2013-01-21 6:20 ` Shawn Guo
2013-01-21 5:53 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2012-07-06 6:14 Stephen Rothwell
2012-07-06 7:01 ` Linus Walleij
2012-07-06 8:55 ` Kuninori Morimoto
2012-07-08 19:14 ` Linus Walleij
2012-07-09 2:04 ` Kuninori Morimoto
2012-07-09 20:34 ` Linus Walleij
2012-07-24 3:56 ` Kuninori Morimoto
2012-08-22 5:03 ` Kuninori Morimoto
2012-08-23 21:43 ` Linus Walleij
2012-08-27 1:16 ` Kuninori Morimoto
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=20130118140346.3f9b182aa7daa175b4f136bf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=shawn.guo@linaro.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).