Received-SPF: pass (google.com: domain of linux-kernel+bounces-168976-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>, 
 Jason Gunthorpe <jgg@ziepe.ca>, linux-rdma@vger.kernel.org, 
 linux-kernel@vger.kernel.org, 
 =?utf-8?q?Ilpo_J=C3=A4rvinen?= <ilpo.jarvinen@linux.intel.com>
Cc: Lukas Wunner <lukas@wunner.de>, 
 Dean Luick <dean.luick@cornelisnetworks.com>
In-Reply-To: <20240503133640.15899-1-ilpo.jarvinen@linux.intel.com>
References: <20240503133640.15899-1-ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v2 1/1] RDMA/hfi1: Use RMW accessors for changing
 LNKCTL2
Message-Id: <171491471637.194239.11215634092351988199.b4-ty@kernel.org>
Date: Sun, 05 May 2024 16:11:56 +0300
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


On Fri, 03 May 2024 16:36:40 +0300, 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.
> 
> In addition, this futureproofs the code. 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 to avoid losing concurrent
> updates (LNKCTL2 is not yet among the registers that need protection
> but likely will be in the future).
> 
> [...]

Applied, thanks!

[1/1] RDMA/hfi1: Use RMW accessors for changing LNKCTL2
      https://git.kernel.org/rdma/rdma/c/8f3b7103b41314

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>