linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: 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>,
	Jamie Iles <jamie@jamieiles.com>, Alan Tull <atull@altera.com>
Subject: Re: linux-next: build warning after merge of the gpio tree
Date: Fri, 7 Mar 2014 14:16:58 +0800	[thread overview]
Message-ID: <CACRpkdZ4mbmQjjhbEHKZwGfSX2AY9+RE4A1oPmaSO4Bn3RFgvw@mail.gmail.com> (raw)
In-Reply-To: <20140307145925.8f09601ffcefcc65e7837e72@canb.auug.org.au>

On Fri, Mar 7, 2014 at 11:59 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Linus,
>
> After merging the gpio tree, today's (and yesterday's) linux-next build
> (x86_64 allmodconfig among others) produced this warning:
>
> kernel/irq/Kconfig:41:error: recursive dependency detected!
> kernel/irq/Kconfig:41:  symbol GENERIC_IRQ_CHIP is selected by GPIO_DWAPB
> drivers/gpio/Kconfig:131:       symbol GPIO_DWAPB depends on IRQ_DOMAIN
> kernel/irq/Kconfig:46:  symbol IRQ_DOMAIN is selected by GENERIC_IRQ_CHIP
>
> Caused by commit 7779b3455697 ("gpio: add a driver for the Synopsys
> DesignWare APB GPIO block").

Thanks Stephen, I merged a patch from Alan Tull earlier today fixing this
problem.

Yours,
Linus Walleij

  reply	other threads:[~2014-03-07  6:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  3:59 linux-next: build warning after merge of the gpio tree Stephen Rothwell
2014-03-07  6:16 ` Linus Walleij [this message]
2016-06-16  4:32 Stephen Rothwell
2016-06-16 10:02 ` Linus Walleij
2016-09-13  3:18 Stephen Rothwell
2016-11-14  5:31 Stephen Rothwell
2017-05-30  3:52 Stephen Rothwell
2018-01-11  4:06 Stephen Rothwell
2018-01-11  9:19 ` Linus Walleij
2018-11-06  1:15 Stephen Rothwell
2018-11-06  7:24 ` Uwe Kleine-König
2018-12-18  5:41 Stephen Rothwell
2019-02-25  4:52 Stephen Rothwell
2019-06-27  8:19 Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij
2019-11-05  6:43 Stephen Rothwell
2019-11-07  8:35 ` Linus Walleij
2020-01-09  4:16 Stephen Rothwell
2020-10-02  8:36 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=CACRpkdZ4mbmQjjhbEHKZwGfSX2AY9+RE4A1oPmaSO4Bn3RFgvw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=atull@altera.com \
    --cc=jamie@jamieiles.com \
    --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).