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] [thread-next>] [day] [month] [year] [list]
Date: Fri, 3 May 2024 10:04:16 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: Alex Deucher <alexander.deucher@....com>, amd-gfx@...ts.freedesktop.org,
	Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...il.com>,
	Dennis Dalessandro <dennis.dalessandro@...nelisnetworks.com>,
	dri-devel@...ts.freedesktop.org, Leon Romanovsky <leon@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-rdma@...r.kernel.org,
	"Pan, Xinhui" <Xinhui.Pan@....com>,
	Christian König <christian.koenig@....com>,
	Lukas Wunner <lukas@...ner.de>,
	Dean Luick <dean.luick@...nelisnetworks.com>
Subject: Re: [PATCH 3/3] RDMA/hfi1: Use RMW accessors for changing LNKCTL2

On Fri, May 03, 2024 at 01:18:35PM +0300, Ilpo Järvinen wrote:
> On Thu, 15 Feb 2024, Ilpo Järvinen wrote:
> 
> > Convert open coded RMW accesses for LNKCTL2 to use
> > pcie_capability_clear_and_set_word() which makes its easier to
> > understand what the code tries to do.
> > 
> > LNKCTL2 is not really owned by any driver because it is a collection of
> > control bits that PCI core might need to touch. RMW accessors already
> > have support for proper locking for a selected set of registers
> > (LNKCTL2 is not yet among them but likely will be in the future) to
> > avoid losing concurrent updates.
> > 
> > Suggested-by: Lukas Wunner <lukas@...ner.de>
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
> > Reviewed-by: Dean Luick <dean.luick@...nelisnetworks.com>
> 
> I found out from Linux RDMA and InfiniBand patchwork that this patch had 
> been silently closed as "Not Applicable". Is there some reason for
> that?

It is part of a series that crosses subsystems, series like that
usually go through some other trees.

If you want single patches applied then please send single
patches.. It is hard to understand intent from mixed series.

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ