From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Subject: Re: linux-next: build warning after merge of the gpio tree
Date: Thu, 11 Jan 2018 10:19:49 +0100 [thread overview]
Message-ID: <CACRpkdYoJ6U6zYoqcLPHO=kN45AcE3YNDdHaOkZNts41XMSgwA@mail.gmail.com> (raw)
In-Reply-To: <20180111150614.2a1d0de0@canb.auug.org.au>
On Thu, Jan 11, 2018 at 5:06 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Linus,
>
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpio/Kconfig:13:error: recursive dependency detected!
> drivers/gpio/Kconfig:13: symbol GPIOLIB is selected by STX104
> drivers/iio/adc/Kconfig:699: symbol STX104 depends on ISA_BUS_API
> arch/Kconfig:821: symbol ISA_BUS_API is selected by GPIO_WINBOND
> drivers/gpio/Kconfig:701: symbol GPIO_WINBOND depends on GPIOLIB
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
>
> Presumably introduced by commit
>
> a0d65009411c ("gpio: winbond: Add driver")
Thanks, Arnd already patched it up quickly!
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-01-11 9:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 4:06 linux-next: build warning after merge of the gpio tree Stephen Rothwell
2018-01-11 9:19 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 8:36 Stephen Rothwell
2020-01-09 4:16 Stephen Rothwell
2019-11-05 6:43 Stephen Rothwell
2019-11-07 8:35 ` Linus Walleij
2019-06-27 8:19 Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij
2019-02-25 4:52 Stephen Rothwell
2018-12-18 5:41 Stephen Rothwell
2018-11-06 1:15 Stephen Rothwell
2018-11-06 7:24 ` Uwe Kleine-König
2017-05-30 3:52 Stephen Rothwell
2016-11-14 5:31 Stephen Rothwell
2016-09-13 3:18 Stephen Rothwell
2016-06-16 4:32 Stephen Rothwell
2016-06-16 10:02 ` Linus Walleij
2014-03-07 3:59 Stephen Rothwell
2014-03-07 6:16 ` Linus Walleij
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='CACRpkdYoJ6U6zYoqcLPHO=kN45AcE3YNDdHaOkZNts41XMSgwA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--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).