From: Bjorn Helgaas <helgaas@kernel.org>
To: Haakon Bugge <haakon.bugge@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Alex Williamson <alex@shazbot.org>,
Johannes Thumshirn <morbidrsa@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] PCI: Initialize RCB from pci_configure_device
Date: Wed, 28 Jan 2026 11:20:53 -0600 [thread overview]
Message-ID: <20260128172053.GA422887@bhelgaas> (raw)
In-Reply-To: <B6127BDA-03D1-4BFB-BA69-A91DC452BE9D@oracle.com>
On Wed, Jan 28, 2026 at 05:08:23PM +0000, Haakon Bugge wrote:
> > On Thu, Jan 22, 2026 at 02:09:53PM +0100, Håkon Bugge wrote:
> >> Commit e42010d8207f ("PCI: Set Read Completion Boundary to 128 iff
> >> Root Port supports it (_HPX)") fixed a bogus _HPX type 2 record, which
> >> instructed program_hpx_type2() to set the RCB in an endpoint,
> >> although it's RC did not have the RCB bit set.
> >> ...
> For this and the other commit, is it OK that I add
> you as a co-developer? Aka:
>
> Co-developed-by: Bjorn Helgaas <helgaas@kernel.org>
> Signed-off-by: Bjorn Helgaas <helgaas@kernel.org>
> Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
No need for co-developed-by, IMO this is just part of normal patch
iteration. And I'll add my Signed-off-by when merging the patches.
> > + pcie_capability_clear_and_set_word(dev, PCI_EXP_LNKCTL,
> > + PCI_EXP_LNKCTL_RCB,
> > + (rp_lnkctl & PCI_EXP_LNKCTL_RCB) ?
> > + PCI_EXP_LNKCTL_RCB : 0);
>
> Looks good to me! This will enforce the locked flavour of
> pcie_capability_clear_and_set_word(). Is that an overkill?
Probably no need for locking in this instance, but it's a per-device
lock so there won't be any contention anyway.
Bjorn
next prev parent reply other threads:[~2026-01-28 17:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 13:09 [PATCH v3 0/2] PCI: Init RCB from pci_configure_device and fix program_hpx_type2 Håkon Bugge
2026-01-22 13:09 ` [PATCH v3 1/2] PCI: Initialize RCB from pci_configure_device Håkon Bugge
2026-01-22 13:45 ` Ilpo Järvinen
2026-01-22 15:53 ` Haakon Bugge
2026-01-27 21:58 ` Bjorn Helgaas
2026-01-23 13:05 ` Niklas Schnelle
2026-01-23 17:38 ` Haakon Bugge
2026-01-23 18:54 ` Niklas Schnelle
2026-01-27 17:28 ` Haakon Bugge
2026-01-27 22:11 ` Bjorn Helgaas
2026-01-28 17:08 ` Haakon Bugge
2026-01-28 17:20 ` Bjorn Helgaas [this message]
2026-01-22 13:09 ` [PATCH v3 2/2] PCI/ACPI: Confine program_hpx_type2 to the AER bits Håkon Bugge
2026-01-27 22:24 ` Bjorn Helgaas
2026-01-28 17:19 ` Haakon Bugge
2026-01-29 16:36 ` Haakon Bugge
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=20260128172053.GA422887@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex@shazbot.org \
--cc=bhelgaas@google.com \
--cc=haakon.bugge@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=morbidrsa@gmail.com \
--cc=schnelle@linux.ibm.com \
/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