netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: roopa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, colin.king@canonical.com,
	nikolay@cumulusnetworks.com
Subject: Re: [PATCH net-next] bridge: vlan tunnel id info range fill size calc cleanups
Date: Wed, 08 Feb 2017 14:39:32 -0500 (EST)	[thread overview]
Message-ID: <20170208.143932.1043944264336559559.davem@davemloft.net> (raw)
In-Reply-To: <1486512720-1071-1-git-send-email-roopa@cumulusnetworks.com>

From: Roopa Prabhu <roopa@cumulusnetworks.com>
Date: Tue,  7 Feb 2017 16:12:00 -0800

> From: Roopa Prabhu <roopa@cumulusnetworks.com>
> 
> This fixes a bug and cleans up tunnelid range size
> calculation code by using consistent variable names
> and checks in size calculation and fill functions.
> 
> tested for a few cases of vlan-vni range mappings:
> (output from patched iproute2):
> $bridge vlan showtunnel
> port     vid        tunid
> vxlan0   100-105    1000-1005
>          200        2000
>          210        2100
>          211-213    2100-2102
>          214        2104
>          216-217    2108-2109
>          219        2119
> 
> Fixes: efa5356b0d97 ("bridge: per vlan dst_metadata netlink support")
> Reported-by: Colin Ian King <colin.king@canonical.com>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>

Applied, thanks Roopa.

      reply	other threads:[~2017-02-08 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  0:12 [PATCH net-next] bridge: vlan tunnel id info range fill size calc cleanups Roopa Prabhu
2017-02-08 19:39 ` David Miller [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=20170208.143932.1043944264336559559.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=colin.king@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.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).