lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240701070832.GA13195@unreal>
Date: Mon, 1 Jul 2024 10:08:32 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Doug Ledford <dledford@...hat.com>, Jason Gunthorpe <jgg@...lanox.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the mlx5-next tree

On Mon, Jul 01, 2024 at 03:36:01PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the rdma tree as a different commit
> (but the same patch):
> 
>   78a6cbd5145c ("RDMA/mlx5: Use sq timestamp as QP timestamp when RoCE is disabled")
> 
> This is commit
> 
>   0c5275bf75ec ("RDMA/mlx5: Use sq timestamp as QP timestamp when RoCE is disabled")
> 
> in the rdma tree.

It is safe to drop the commit from mlx5-next, I dropped it now.

Thanks

> 
> -- 
> Cheers,
> Stephen Rothwell



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ