[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200125.134907.81338433085133777.davem@davemloft.net>
Date: Sat, 25 Jan 2020 13:49:07 +0100 (CET)
From: David Miller <davem@...emloft.net>
To: saeedm@...lanox.com
Cc: netdev@...r.kernel.org
Subject: Re: [pull request][net 0/9] Mellanox, mlx5 fixes 2020-01-24
From: Saeed Mahameed <saeedm@...lanox.com>
Date: Fri, 24 Jan 2020 20:20:50 +0000
> This series introduces some fixes to mlx5 driver.
>
> Please pull and let me know if there is any problem.
Pulled.
> Merge conflict: once merge with net-next, a contextual conflict will
> appear in drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
> since the code moved in net-next.
> To resolve, just delete ALL of the conflicting hunk from net.
> So sorry for the small mess ..
Thanks for the heads up.
> For -stable v5.4:
> ('net/mlx5: Update the list of the PCI supported devices')
> ('net/mlx5: Fix lowest FDB pool size')
> ('net/mlx5e: kTLS, Fix corner-case checks in TX resync flow')
> ('net/mlx5e: kTLS, Do not send decrypted-marked SKBs via non-accel path')
> ('net/mlx5: Eswitch, Prevent ingress rate configuration of uplink rep')
> ('net/mlx5e: kTLS, Remove redundant posts in TX resync flow')
> ('net/mlx5: DR, Enable counter on non-fwd-dest objects')
> ('net/mlx5: DR, use non preemptible call to get the current cpu number')
Queued up.
Powered by blists - more mailing lists