[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f2e3fb5789270a6106510138211e5c17f3c7ad7.camel@mellanox.com>
Date: Fri, 6 Mar 2020 00:52:24 +0000
From: Saeed Mahameed <saeedm@...lanox.com>
To: "kuba@...nel.org" <kuba@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [pull request][net 0/5] Mellanox, mlx5 fixes 2020-03-05
On Thu, 2020-03-05 at 15:56 -0800, Jakub Kicinski wrote:
> On Thu, 5 Mar 2020 15:17:34 -0800 Saeed Mahameed wrote:
> > Hi Dave,
> >
> > This series introduces some fixes to mlx5 driver.
> >
> > Please pull and let me know if there is any problem.
> >
> > For -stable v5.3
> > ('net/mlx5e: kTLS, Fix wrong value in record tracker enum')
>
> Back porting dead code feels kinda weird :S
>
Yes this one can be skipped.
I have an automatic system that already tries to backport and test the
patch to find the correct -stable to mark, and this time I didn't
double check manually if the patch is actually needed to be backported
.. my bad.
> > For -stable v5.4
> > ('net/mlx5: DR, Fix postsend actions write length')
> >
> > For -stable v5.5
> > ('net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow')
> > ('net/mlx5e: Fix endianness handling in pedit mask')
>
> I can only trust your testing on the pedit change :)
>
> Reviewed-by: Jakub Kicinski <kuba@...nel.org>
Thanks!
Powered by blists - more mailing lists