From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: festevam@gmail.com, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, fabio.estevam@freescale.com,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] net: bridge: netfilter: Fix dependency for BRIDGE_NF_EBTABLES
Date: Tue, 10 Jan 2012 22:32:05 -0800 (PST) [thread overview]
Message-ID: <20120110.223205.265079469678742211.davem@davemloft.net> (raw)
In-Reply-To: <20120110175251.4b6ad831@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Tue, 10 Jan 2012 17:52:51 -0800
> On Tue, 10 Jan 2012 23:48:25 -0200
> Fabio Estevam <festevam@gmail.com> wrote:
>
>> Fix the following build warning:
>>
>> warning: (BRIDGE_NF_EBTABLES) selects NETFILTER_XTABLES which has unmet direct dependencies (NET && INET && NETFILTER)
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
>> net/bridge/netfilter/Kconfig | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/net/bridge/netfilter/Kconfig b/net/bridge/netfilter/Kconfig
>> index a9aff9c..9ca621a 100644
>> --- a/net/bridge/netfilter/Kconfig
>> +++ b/net/bridge/netfilter/Kconfig
>> @@ -4,7 +4,7 @@
>>
>> menuconfig BRIDGE_NF_EBTABLES
>> tristate "Ethernet Bridge tables (ebtables) support"
>> - depends on BRIDGE && NETFILTER
>> + depends on BRIDGE && NETFILTER && INET
>> select NETFILTER_XTABLES
>> help
>> ebtables is a general, extensible frame/packet identification
>
> Almost everybody has INET defined... but still it should be possible to run ebtables
> without INET layer. Looks like a but in XTABLES to me.
And this needs to be CC:'d to the netfilter folks meanwhile, added...
parent reply other threads:[~2012-01-11 6:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120110175251.4b6ad831@nehalam.linuxnetplumber.net>]
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=20120110.223205.265079469678742211.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).