From: Paul Blakey <paulb@nvidia.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: <netdev@vger.kernel.org>, Jamal Hadi Salim <jhs@mojatatu.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
Vlad Buslov <vladbu@nvidia.com>, Oz Shlomo <ozsh@nvidia.com>,
Roi Dayan <roid@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH net-next 3/3] net/mlx5: CT: Add support for matching on ct_state reply flag
Date: Wed, 3 Feb 2021 09:58:12 +0200 [thread overview]
Message-ID: <eb6f26e0-c8be-ccab-8fe9-d9c15a1ea9ab@nvidia.com> (raw)
In-Reply-To: <20210202123659.GA3405@horizon.localdomain>
On Tue, 2 Feb 2021, Marcelo Ricardo Leitner wrote:
> On Wed, Jan 27, 2021 at 04:32:47PM +0200, Paul Blakey wrote:
> > Add support for matching on ct_state reply flag.
>
> Sorry for the late reply, missed the patchset here. (just noticed
> because of the iproute2 patch, thanks for the Cc in there)
>
> Only one question though. Is it safe to assume that this will require
> a firmware update as well?
No, it will not, there was room for this flag in the register before (as
long as you had a firmware recent enough that supported CT feature
itself ofc).
Paul.
>
> Thanks,
> Marcelo
>
next prev parent reply other threads:[~2021-02-03 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 14:32 [PATCH net-next 0/3] net/sched: cls_flower: Add support for matching on ct_state reply flag Paul Blakey
2021-01-27 14:32 ` [PATCH net-next 1/3] net/sched: cls_flower: Add match on the " Paul Blakey
2021-01-27 14:32 ` [PATCH net-next 2/3] net: flow_offload: Add original direction flag to ct_metadata Paul Blakey
2021-01-27 14:32 ` [PATCH net-next 3/3] net/mlx5: CT: Add support for matching on ct_state reply flag Paul Blakey
2021-02-02 12:36 ` Marcelo Ricardo Leitner
2021-02-03 7:58 ` Paul Blakey [this message]
2021-01-30 2:30 ` [PATCH net-next 0/3] net/sched: cls_flower: " patchwork-bot+netdevbpf
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=eb6f26e0-c8be-ccab-8fe9-d9c15a1ea9ab@nvidia.com \
--to=paulb@nvidia.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.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).