From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Paul Thompson <set.mailinglist@gmail•com>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: linux-next: build warning after merge of the final tree
Date: Mon, 17 Dec 2012 12:59:33 -0800 [thread overview]
Message-ID: <20121217125933.ec758888.akpm@linux-foundation.org> (raw)
In-Reply-To: <20121217143415.252a2f60076d1ba03807df55@canb.auug.org.au>
On Mon, 17 Dec 2012 14:34:15 +1100
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> On Mon, 17 Dec 2012 14:22:38 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > After merging the final tree, today's linux-next build (powerpc allnoconfig)
> > produced this warning:
> >
> > warning: (PPC) selects SPARSE_IRQ which has unmet direct dependencies (HAVE_GENERIC_HARDIRQS && (IRQ_DOMAIN && DEBUG_FS || MAY_HAVE_SPARSE_IRQ))
> >
> > I don't know what introduced that.
>
> Actually probably caused by commit a1eaa3bc8247 ("Kconfig: fix Irq
> Subsystem menu") from the akpm tree.
kconfig-fix-irq-subsystem-menu.patch was causing various problems so I
have dropped it.
next prev parent reply other threads:[~2012-12-17 20:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 3:22 linux-next: build warning after merge of the final tree Stephen Rothwell
2012-12-17 3:34 ` Stephen Rothwell
2012-12-17 20:59 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 5:29 Stephen Rothwell
2013-05-29 5:44 ` David Miller
2013-04-19 8:07 Stephen Rothwell
2013-04-19 9:44 ` Joerg Roedel
2012-08-02 4:04 Stephen Rothwell
2012-08-02 14:45 ` Nathan Zimmer
2012-03-26 4:11 Stephen Rothwell
2012-03-28 7:59 ` Williams, Dan J
2011-08-16 5:22 Stephen Rothwell
2011-08-16 6:04 ` Herbert Xu
2011-08-16 7:03 ` Stephen Rothwell
2011-08-16 7:08 ` Herbert Xu
2011-07-22 6:24 Stephen Rothwell
2011-07-22 6:26 ` David Miller
2010-09-29 4:02 Stephen Rothwell
2010-09-16 5:05 Stephen Rothwell
2010-09-16 6:29 ` Jens Axboe
2010-05-26 5:15 Stephen Rothwell
2010-03-01 8:14 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=20121217125933.ec758888.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=set.mailinglist@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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