From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, matt@ozlabs.org
Subject: Re: linux-next: build warning after merge of the final tree
Date: Thu, 21 Jul 2011 23:26:51 -0700 (PDT) [thread overview]
Message-ID: <20110721.232651.1449248174820939714.davem@davemloft.net> (raw)
In-Reply-To: <20110722162433.a280b3b71cff9c08fe18956f@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 22 Jul 2011 16:24:33 +1000
> warning: (PPC) selects HAVE_BPF_JIT which has unmet direct dependencies (NET)
>
> Introduced by commit 0ca87f05ba8b ("net: filter: BPF 'JIT' compiler for
> PPC64").
>
> I suspect that the fix is to move the
>
> config HAVE_BPF_JIT
> bool
>
> lines to outside the "if NET" in net/Kconfig.
I'm going to fix this the way it's dealt with in the x86_64 case
for now, thanks for the report:
--------------------
net: Fix ppc64 BPF JIT dependencies.
Signed-off-by: David S. Miller <davem@davemloft.net>
---
arch/powerpc/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 39860fc..cdf7a0a 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@ -134,7 +134,7 @@ config PPC
select GENERIC_IRQ_SHOW_LEVEL
select HAVE_RCU_TABLE_FREE if SMP
select HAVE_SYSCALL_TRACEPOINTS
- select HAVE_BPF_JIT if PPC64
+ select HAVE_BPF_JIT if (PPC64 && NET)
config EARLY_PRINTK
bool
--
1.7.6
next prev parent reply other threads:[~2011-07-22 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 6:24 linux-next: build warning after merge of the final tree Stephen Rothwell
2011-07-22 6:26 ` David Miller [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
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=20110721.232651.1449248174820939714.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matt@ozlabs.org \
--cc=netdev@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).