From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
kyeyoonp@codeaurora.org, jouni@codeaurora.org,
davem@davemloft.net
Subject: Re: [PATCH net 0/2] bridge: netlink: add missing policy entries and sizes
Date: Tue, 4 Aug 2015 16:54:14 -0700 [thread overview]
Message-ID: <20150804165414.0332926d@urahara> (raw)
In-Reply-To: <1438707993-14561-1-git-send-email-razor@blackwall.org>
On Tue, 4 Aug 2015 19:06:31 +0200
Nikolay Aleksandrov <razor@blackwall.org> wrote:
> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>
> Hi,
> When IFLA_BRPORT_PROXYARP and PROXYARP_WIFI were introduced they weren't
> accounted for in the get_slave_size() callback and didn't get a policy
> entry, so fix it now. Sending as two separate patches because the first
> one goes further back than the second and thus we get 2 different Fixes
> tags.
>
> Cheers,
> Nik
>
> Nikolay Aleksandrov (2):
> bridge: netlink: account for the IFLA_BRPORT_PROXYARP attribute size
> and policy
> bridge: netlink: account for the IFLA_BRPORT_PROXYARP_WIFI attribute
> size and policy
>
> net/bridge/br_netlink.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
prev parent reply other threads:[~2015-08-04 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 17:06 [PATCH net 0/2] bridge: netlink: add missing policy entries and sizes Nikolay Aleksandrov
2015-08-04 17:06 ` [PATCH net 1/2] bridge: netlink: account for the IFLA_BRPORT_PROXYARP attribute size and policy Nikolay Aleksandrov
2015-08-07 6:55 ` David Miller
2015-08-04 17:06 ` [PATCH net 2/2] bridge: netlink: account for the IFLA_BRPORT_PROXYARP_WIFI " Nikolay Aleksandrov
2015-08-07 6:55 ` David Miller
2015-08-04 23:54 ` Stephen Hemminger [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=20150804165414.0332926d@urahara \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jouni@codeaurora.org \
--cc=kyeyoonp@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=razor@blackwall.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