From: Jiri Benc <jbenc@redhat.com>
To: Pravin B Shelar <pshelar@nicira.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] openvswitch: Fix incorrect type use.
Date: Wed, 21 Oct 2015 13:30:01 +0200 [thread overview]
Message-ID: <20151021133001.5e5af057@griffin> (raw)
In-Reply-To: <1445399266-2034-1-git-send-email-pshelar@nicira.com>
On Tue, 20 Oct 2015 20:47:46 -0700, Pravin B Shelar wrote:
> --- a/net/openvswitch/flow_netlink.c
> +++ b/net/openvswitch/flow_netlink.c
> @@ -548,11 +548,11 @@ static int ip_tun_from_nlattr(const struct nlattr *attr,
> struct sw_flow_match *match, bool is_mask,
> bool log)
> {
> + bool ttl = false, ipv4 = false, ipv6 = false;
> + __be16 tun_flags = 0;
> + int opts_type = 0;
> struct nlattr *a;
> int rem;
> - bool ttl = false;
> - __be16 tun_flags = 0, ipv4 = false, ipv6 = false;
> - int opts_type = 0;
Seems that I appended the variables to a wrong line during one of the
rebases. Thanks for fixing this.
Acked-by: Jiri Benc <jbenc@redhat.com>
--
Jiri Benc
next prev parent reply other threads:[~2015-10-21 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 3:47 [PATCH net-next] openvswitch: Fix incorrect type use Pravin B Shelar
2015-10-21 8:21 ` Thomas Graf
2015-10-21 11:30 ` Jiri Benc [this message]
2015-10-22 13:46 ` David Miller
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=20151021133001.5e5af057@griffin \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.