From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net 00/12] Mellanox, mlx5 fixes 2019-08-08
Date: Fri, 09 Aug 2019 13:37:06 -0700 (PDT) [thread overview]
Message-ID: <20190809.133706.1598956680657409884.davem@davemloft.net> (raw)
In-Reply-To: <20190808202025.11303-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Thu, 8 Aug 2019 20:21:58 +0000
> This series introduces some fixes to mlx5 driver.
>
> Highlights:
> 1) From Tariq, Critical mlx5 kTLS fixes to better align with hw specs.
> 2) From Aya, Fixes to mlx5 tx devlink health reporter.
> 3) From Maxim, aRFs parsing to use flow dissector to avoid relying on
> invalid skb fields.
>
> Please pull and let me know if there is any problem.
Pulled.
> For -stable v4.3
> ('net/mlx5e: Only support tx/rx pause setting for port owner')
> For -stable v4.9
> ('net/mlx5e: Use flow keys dissector to parse packets for ARFS')
> For -stable v5.1
> ('net/mlx5e: Fix false negative indication on tx reporter CQE recovery')
> ('net/mlx5e: Remove redundant check in CQE recovery flow of tx reporter')
> ('net/mlx5e: ethtool, Avoid setting speed to 56GBASE when autoneg off')
Queued up.
> Note: when merged with net-next this minor conflict will pop up:
> ++<<<<<<< (net-next)
> + if (is_eswitch_flow) {
> + flow->esw_attr->match_level = match_level;
> + flow->esw_attr->tunnel_match_level = tunnel_match_level;
> ++=======
> + if (flow->flags & MLX5E_TC_FLOW_ESWITCH) {
> + flow->esw_attr->inner_match_level = inner_match_level;
> + flow->esw_attr->outer_match_level = outer_match_level;
> ++>>>>>>> (net)
>
> To resolve, use hunks from net (2nd) and replace:
> if (flow->flags & MLX5E_TC_FLOW_ESWITCH)
> with
> if (is_eswitch_flow)
Thanks for this.
prev parent reply other threads:[~2019-08-09 20:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 20:21 [pull request][net 00/12] Mellanox, mlx5 fixes 2019-08-08 Saeed Mahameed
2019-08-08 20:22 ` [net 01/12] net/mlx5e: Use flow keys dissector to parse packets for ARFS Saeed Mahameed
2019-08-09 1:15 ` Jakub Kicinski
2019-08-09 18:49 ` Saeed Mahameed
2019-08-09 19:01 ` Jakub Kicinski
2019-08-08 20:22 ` [net 02/12] net/mlx5: Support inner header match criteria for non decap flow action Saeed Mahameed
2019-08-08 20:22 ` [net 03/12] net/mlx5e: Only support tx/rx pause setting for port owner Saeed Mahameed
2019-08-08 20:22 ` [net 04/12] net/mlx5e: ethtool, Avoid setting speed to 56GBASE when autoneg off Saeed Mahameed
2019-08-08 20:22 ` [net 05/12] net/mlx5: crypto, Fix wrong offset in encryption key command Saeed Mahameed
2019-08-08 20:22 ` [net 06/12] net/mlx5: kTLS, Fix wrong TIS opmod constants Saeed Mahameed
2019-08-08 20:22 ` [net 07/12] net/mlx5e: kTLS, Fix progress params context WQE layout Saeed Mahameed
2019-08-08 20:22 ` [net 08/12] net/mlx5e: kTLS, Fix tisn field name Saeed Mahameed
2019-08-08 20:22 ` [net 09/12] net/mlx5e: kTLS, Fix tisn field placement Saeed Mahameed
2019-08-08 20:22 ` [net 10/12] net/mlx5e: Fix false negative indication on tx reporter CQE recovery Saeed Mahameed
2019-08-08 20:22 ` [net 11/12] net/mlx5e: Fix error flow of CQE recovery on tx reporter Saeed Mahameed
2019-08-08 20:22 ` [net 12/12] net/mlx5e: Remove redundant check in CQE recovery flow of " Saeed Mahameed
2019-08-09 20:37 ` 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=20190809.133706.1598956680657409884.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).