From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: roopa@cumulusnetworks.com, netdev@vger.kernel.org,
nikolay@cumulusnetworks.com, idosch@mellanox.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next v2 0/5] fib_rules: support sport, dport and proto match
Date: Wed, 28 Feb 2018 14:30:58 -0500 (EST) [thread overview]
Message-ID: <20180228.143058.834163830127082943.davem@davemloft.net> (raw)
In-Reply-To: <597ab09e-d0bd-123d-2d54-cca679e69847@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Wed, 28 Feb 2018 11:11:43 -0700
> Hi Dave: I'm not seeing it in your tree yet. I've been waiting on this
> set for the next version of the L4 hashing for IPv6.
Just pushed out, build test was still running :-)
prev parent reply other threads:[~2018-02-28 19:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 3:52 [PATCH net-next v2 0/5] fib_rules: support sport, dport and proto match Roopa Prabhu
2018-02-28 3:52 ` [PATCH net-next v2 1/5] net: fib_rules: support for match on ip_proto, sport and dport Roopa Prabhu
2018-02-28 13:08 ` Nikolay Aleksandrov
2018-03-01 22:48 ` Eric Dumazet
2018-03-01 23:08 ` Roopa Prabhu
2018-02-28 3:52 ` [PATCH net-next v2 2/5] ipv4: fib_rules: support match on sport, dport and ip proto Roopa Prabhu
2018-02-28 13:09 ` Nikolay Aleksandrov
2018-02-28 3:52 ` [PATCH net-next v2 3/5] ipv6: fib6_rules: support for " Roopa Prabhu
2018-02-28 13:10 ` Nikolay Aleksandrov
2018-02-28 3:52 ` [PATCH net-next v2 4/5] ipv4: route: dissect flow in input path if fib rules need it Roopa Prabhu
2018-02-28 9:59 ` Paolo Abeni
2018-02-28 13:13 ` Nikolay Aleksandrov
2018-02-28 3:52 ` [PATCH net-next v2 5/5] ipv6: " Roopa Prabhu
2018-02-28 10:05 ` Paolo Abeni
2018-02-28 13:20 ` Nikolay Aleksandrov
2018-02-28 16:59 ` [PATCH net-next v2 0/5] fib_rules: support sport, dport and proto match David Miller
2018-02-28 18:11 ` David Ahern
2018-02-28 19:30 ` 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=20180228.143058.834163830127082943.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=pabeni@redhat.com \
--cc=roopa@cumulusnetworks.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 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).