From: David Miller <davem@davemloft.net>
To: rami.rosen@intel.com
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
stephen@networkplumber.org
Subject: Re: [PATCH net-next v2] bridge: Fix setting a flag in br_fill_ifvlaninfo_range().
Date: Fri, 24 Jul 2015 22:57:55 -0700 (PDT) [thread overview]
Message-ID: <20150724.225755.745816746075981554.davem@davemloft.net> (raw)
In-Reply-To: <1437541022-14250-1-git-send-email-rami.rosen@intel.com>
From: Rami Rosen <rami.rosen@intel.com>
Date: Wed, 22 Jul 2015 07:57:02 +0300
> This patch fixes setting of vinfo.flags in the br_fill_ifvlaninfo_range() method. The
> assignment of vinfo.flags &= ~BRIDGE_VLAN_INFO_RANGE_BEGIN has no effect and is
> unneeded, as vinfo.flags value is overriden by the immediately following
> vinfo.flags = flags | BRIDGE_VLAN_INFO_RANGE_END assignement.
>
> Signed-off-by: Rami Rosen <rami.rosen@intel.com>
Applied.
prev parent reply other threads:[~2015-07-25 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 4:57 [PATCH net-next v2] bridge: Fix setting a flag in br_fill_ifvlaninfo_range() Rami Rosen
2015-07-22 5:52 ` roopa
2015-07-25 5:57 ` 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=20150724.225755.745816746075981554.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rami.rosen@intel.com \
--cc=roopa@cumulusnetworks.com \
--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).