From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Paul Blakey <paulb@mellanox.com>
Cc: Jiri Pirko <jiri@mellanox.com>, Roi Dayan <roid@mellanox.com>,
Yossi Kuperman <yossiku@mellanox.com>,
Oz Shlomo <ozsh@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Aaron Conole <aconole@redhat.com>, Zhike Wang <wangzhike@jd.com>,
Rony Efraim <ronye@mellanox.com>,
"nst-kernel@redhat.com" <nst-kernel@redhat.com>,
John Hurley <john.hurley@netronome.com>,
Simon Horman <simon.horman@netronome.com>,
Justin Pettit <jpettit@ovn.org>
Subject: Re: [PATCH net-next iproute2 v2 0/3] net/sched: Introduce tc connection tracking
Date: Thu, 18 Jul 2019 13:52:33 -0300 [thread overview]
Message-ID: <20190718165233.GT3390@localhost.localdomain> (raw)
In-Reply-To: <9286cbad-6821-786a-6882-d2bf56b3cf05@mellanox.com>
On Thu, Jul 18, 2019 at 03:00:34PM +0000, Paul Blakey wrote:
> Hey guys,
>
> any more comments?
From my side, just the man page on tc-ct(8) that is missing.
Everything else seems to be in place.
Thanks,
Marcelo
next prev parent reply other threads:[~2019-07-18 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 8:14 [PATCH net-next iproute2 v2 0/3] net/sched: Introduce tc connection tracking Paul Blakey
2019-07-11 8:14 ` [PATCH net-next iproute2 v2 1/3] tc: add NLA_F_NESTED flag to all actions options nested block Paul Blakey
2019-07-11 8:14 ` [PATCH net-next iproute2 v2 2/3] tc: Introduce tc ct action Paul Blakey
2019-07-11 8:14 ` [PATCH net-next iproute2 v2 3/3] tc: flower: Add matching on conntrack info Paul Blakey
2019-07-18 15:00 ` [PATCH net-next iproute2 v2 0/3] net/sched: Introduce tc connection tracking Paul Blakey
2019-07-18 16:52 ` Marcelo Ricardo Leitner [this message]
2019-07-18 16:58 ` David Ahern
2019-07-18 22:42 ` David Ahern
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=20190718165233.GT3390@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=john.hurley@netronome.com \
--cc=jpettit@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=nst-kernel@redhat.com \
--cc=ozsh@mellanox.com \
--cc=paulb@mellanox.com \
--cc=roid@mellanox.com \
--cc=ronye@mellanox.com \
--cc=simon.horman@netronome.com \
--cc=wangzhike@jd.com \
--cc=yossiku@mellanox.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).