From: Sabrina Dubroca <sd@queasysnail.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>,
Kyeyoon Park <kyeyoonp@codeaurora.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] bridge: make proxy arp configurable
Date: Sun, 30 Nov 2014 19:20:46 +0100 [thread overview]
Message-ID: <20141130182046.GA16296@kria> (raw)
In-Reply-To: <20141130092001.7168dc72@urahara>
Hello Stephen,
2014-11-30, 09:20:01 -0800, Stephen Hemminger wrote:
>
> This solves kernel build without INET enabled, and allows user
> to control enabling this feature.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> ---
> net/bridge/Kconfig | 15 +++++++++++++++
> net/bridge/br_input.c | 4 ++++
> net/bridge/br_sysfs_if.c | 4 ++++
> 3 files changed, 23 insertions(+)
>
> --- a/net/bridge/Kconfig 2014-11-25 09:42:34.687891662 -0800
> +++ b/net/bridge/Kconfig 2014-11-25 09:42:34.683891643 -0800
> @@ -60,3 +60,18 @@ config BRIDGE_VLAN_FILTERING
> Say N to exclude this support and reduce the binary size.
>
> If unsure, say Y.
> +
> +config BRIDGE_ARP_PROXY
Shouldn't this be BRIDGE_PROXY_ARP to match all the
#ifdef CONFIG_BRIDGE_PROXY_ARP
below?
> --- a/net/bridge/br_input.c 2014-11-25 09:42:34.687891662 -0800
> +++ b/net/bridge/br_input.c 2014-11-25 09:42:34.683891643 -0800
> @@ -59,6 +59,7 @@ static int br_pass_frame_up(struct sk_bu
> netif_receive_skb);
> }
>
> +#ifdef CONFIG_BRIDGE_PROXY_ARP
> static void br_do_proxy_arp(struct sk_buff *skb, struct net_bridge *br,
> u16 vid)
> {
> @@ -112,6 +113,7 @@ static void br_do_proxy_arp(struct sk_bu
> neigh_release(n);
> }
> }
> +#endif
--
Sabrina
prev parent reply other threads:[~2014-11-30 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 17:20 [PATCH net-next v2] bridge: make proxy arp configurable Stephen Hemminger
2014-11-30 18:20 ` Sabrina Dubroca [this message]
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=20141130182046.GA16296@kria \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=kyeyoonp@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).