From: Richard Gobert <richardbgobert@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, idosch@nvidia.com, razor@blackwall.org,
amcohen@nvidia.com, petrm@nvidia.com, jbenc@redhat.com,
b.galvani@gmail.com, bpoirier@nvidia.com, gavinl@nvidia.com,
martin.lau@kernel.org, daniel@iogearbox.net,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] net: add local address bind support to vxlan and geneve
Date: Thu, 22 Feb 2024 21:48:39 +0100 [thread overview]
Message-ID: <df300a49-7811-4126-a56a-a77100c8841b@gmail.com> (raw)
This series adds local address bind support to both vxlan
and geneve sockets.
Richard Gobert (2):
net: vxlan: enable local address bind for vxlan sockets
net: geneve: enable local address bind for geneve sockets
drivers/net/geneve.c | 58 +++++++++++++++++++++++++++---
drivers/net/vxlan/vxlan_core.c | 19 +++++++---
include/net/geneve.h | 6 ++++
include/uapi/linux/if_link.h | 2 ++
tools/include/uapi/linux/if_link.h | 2 ++
5 files changed, 77 insertions(+), 10 deletions(-)
--
2.36.1
next reply other threads:[~2024-02-22 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 20:48 Richard Gobert [this message]
2024-02-22 20:51 ` [PATCH net-next 1/2] net: vxlan: enable local address bind for vxlan sockets Richard Gobert
2024-02-23 17:49 ` kernel test robot
2024-02-24 5:58 ` kernel test robot
2024-02-22 20:53 ` [PATCH net-next 2/2] net: geneve: enable local address bind for geneve sockets Richard Gobert
2024-02-22 22:31 ` Eyal Birger
2024-02-27 9:02 ` Richard Gobert
2024-02-28 17:51 ` Eyal Birger
2024-02-24 9:01 ` kernel test robot
2024-02-24 10:06 ` Jiri Benc
2024-02-23 14:11 ` [PATCH net-next 0/2] net: add local address bind support to vxlan and geneve Jakub Kicinski
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=df300a49-7811-4126-a56a-a77100c8841b@gmail.com \
--to=richardbgobert@gmail.com \
--cc=amcohen@nvidia.com \
--cc=b.galvani@gmail.com \
--cc=bpoirier@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gavinl@nvidia.com \
--cc=herbert@gondor.apana.org.au \
--cc=idosch@nvidia.com \
--cc=jbenc@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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;
as well as URLs for NNTP newsgroup(s).