From: David Miller <davem@davemloft.net>
To: tgraf@suug.ch
Cc: netdev@vger.kernel.org, dev@openvswitch.org
Subject: Re: [PATCH net-next] openvswitch: Retrieve tunnel metadata when receiving from vport-netdev
Date: Sun, 26 Jul 2015 21:19:33 -0700 (PDT) [thread overview]
Message-ID: <20150726.211933.409072959161623165.davem@davemloft.net> (raw)
In-Reply-To: <f91747edf4825bd5b6641c5c815d0e20f59b7a3a.1437649446.git.tgraf@suug.ch>
From: Thomas Graf <tgraf@suug.ch>
Date: Thu, 23 Jul 2015 13:04:44 +0200
> Retrieve the tunnel metadata for packets received by a net_device and
> provide it to ovs_vport_receive() for flow key extraction.
>
> [This hunk was in the GRE patch in the initial series and missed the
> cut for the initial submission for merging.]
>
> Fixes: 614732eaa12d ("openvswitch: Use regular VXLAN net_device device")
> Signed-off-by: Thomas Graf <tgraf@suug.ch>
Applied, thanks.
prev parent reply other threads:[~2015-07-27 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 11:04 [PATCH net-next] openvswitch: Retrieve tunnel metadata when receiving from vport-netdev Thomas Graf
2015-07-23 21:13 ` Pravin Shelar
2015-07-27 4:19 ` 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=20150726.211933.409072959161623165.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).