mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Lukas Wunner <lukas@wunner.de>,
	 Dean Luick <dean.luick@cornelisnetworks.com>
Subject: Re: [PATCH v2 1/1] RDMA/hfi1: Use RMW accessors for changing LNKCTL2
Date: Sun, 05 May 2024 16:11:56 +0300	[thread overview]
Message-ID: <171491471637.194239.11215634092351988199.b4-ty@kernel.org> (raw)
In-Reply-To: <20240503133640.15899-1-ilpo.jarvinen@linux.intel.com>


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>


      reply	other threads:[~2024-05-05 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 13:36 Ilpo Järvinen
2024-05-05 13:11 ` Leon Romanovsky [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=171491471637.194239.11215634092351988199.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=dean.luick@cornelisnetworks.com \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lukas@wunner.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®