From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the pinctrl tree
Date: Mon, 19 May 2014 11:03:10 +0200 [thread overview]
Message-ID: <20140519090310.GD29466@lukather> (raw)
In-Reply-To: <20140519165947.619886fc@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Hi Stephen,
On Mon, May 19, 2014 at 04:59:47PM +1000, Stephen Rothwell wrote:
> Hi Linus,
>
> After merging the pinctrl tree, today's linux-next build (x86_64
> allmodconfig among others) produced this warning:
>
> drivers/pinctrl/sunxi/Kconfig:3:error: recursive dependency detected!
> drivers/pinctrl/sunxi/Kconfig:3: symbol PINCTRL_SUNXI is selected by PINCTRL_SUN4I_A10
> drivers/pinctrl/sunxi/Kconfig:9: symbol PINCTRL_SUN4I_A10 default value contains PINCTRL_SUNXI
>
> Introduced by commit 3b582f7e1542 ("pinctrl: sunxi: Enable the pinctrl
> Kconfig options by default").
This should be fixed with the patch I sent on saturday:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/257411.html
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-05-19 9:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 6:59 linux-next: build warning after merge of the pinctrl tree Stephen Rothwell
2014-05-19 9:03 ` Maxime Ripard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-21 7:11 Stephen Rothwell
2022-04-21 14:12 ` Linus Walleij
2022-04-21 18:05 ` Stefan Wahren
2021-10-27 11:01 Stephen Rothwell
2021-10-27 11:10 ` Marc Zyngier
2021-10-28 7:03 ` Mauro Carvalho Chehab
2022-01-20 3:25 ` Stephen Rothwell
2022-03-18 7:31 ` Stephen Rothwell
2022-06-05 23:33 ` Stephen Rothwell
2021-03-30 6:07 Stephen Rothwell
2021-03-30 7:51 ` Linus Walleij
2020-04-17 2:27 Stephen Rothwell
2020-04-17 10:23 ` Linus Walleij
2018-10-11 3:17 Stephen Rothwell
2018-10-11 7:51 ` Linus Walleij
2017-06-30 4:56 Stephen Rothwell
2017-06-30 4:57 ` Stephen Rothwell
2017-06-30 6:59 ` Geert Uytterhoeven
2017-06-30 13:48 ` Linus Walleij
2017-01-03 4:37 Stephen Rothwell
2015-05-20 6:40 Stephen Rothwell
2015-05-20 7:14 ` Linus Walleij
2013-12-13 4:06 Stephen Rothwell
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=20140519090310.GD29466@lukather \
--to=maxime.ripard@free-electrons.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 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).