From: David Ahern <dsa@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsa@cumulusnetworks.com>
Subject: [PATCH net-next v2 0/2] net: l3mdev: Allow send on enslaved interface
Date: Sat, 7 May 2016 16:48:58 -0700 [thread overview]
Message-ID: <1462664940-26678-1-git-send-email-dsa@cumulusnetworks.com> (raw)
First patch preps for the second. The second is required for several use
cases such as ping on an interface and BFD that need to send packets on
a specific interface, including ones enslaved to a VRF device.
v2
- fixed brackets on both patches per comment from DaveM
David Ahern (2):
net: l3mdev: Move get_saddr and rt6_dst
net: l3mdev: Allow send on enslaved interface
drivers/net/vrf.c | 2 ++
include/net/l3mdev.h | 56 +++-------------------------------------------
net/ipv4/route.c | 4 ++++
net/ipv6/route.c | 2 +-
net/l3mdev/l3mdev.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 73 insertions(+), 54 deletions(-)
--
2.1.4
next reply other threads:[~2016-05-07 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 23:48 David Ahern [this message]
2016-05-07 23:48 ` [PATCH net-next 1/2] net: l3mdev: Move get_saddr and rt6_dst David Ahern
2016-05-07 23:49 ` [PATCH net-next 2/2] net: l3mdev: Allow send on enslaved interface David Ahern
2016-05-10 2:34 ` [PATCH net-next v2 0/2] " 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=1462664940-26678-1-git-send-email-dsa@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.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).