From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>, Len Brown <lenb@kernel.org>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] PCI/DPC: Decide DPC ownership with host_bridge->native_dpc
Date: Fri, 20 Nov 2026 12:18:41 -0600 [thread overview]
Message-ID: <20261120181841.GA893187@bhelgaas> (raw)
In-Reply-To: <av7BRHcVkXOGT6yp@wunner.de>
On Thu, Nov 19, 2026 at 10:28:36AM +0100, Lukas Wunner wrote:
> On Wed, Nov 18, 2026 at 06:10:42PM -0600, Bjorn Helgaas wrote:
> > On Wed, Nov 18, 2026 at 10:17:12AM -0800, Kuppuswamy Sathyanarayanan wrote:
> > > This series makes host_bridge->native_dpc the single decider for whether
> > > Linux uses DPC, as Bjorn asked during the review of "Simplify PCIe native
> > > ownership".
> [...]
> > > Patches 1-2 are the two DPC patches from v2 of Lukas's "Error reporting
> > > for AER-incapable devices", which are included here directly.
> > >
> > > https://lore.kernel.org/r/34c9ee153876bac953135b4518035194b7c07c6c.1794997749.git.lukas@wunner.de
> > > https://lore.kernel.org/r/58d8a99cc6c2ecba6dadc450ecb4501d47816732.1794997749.git.lukas@wunner.de
> >
> > Applied to pci/aer for v7.5, thank you!
>
> Hm, it looks like you applied to pci/portdrv instead of pci/aer.
>
> Note that the first two patches in Sathya's series are identical to
> the first two patches of this other pending series...
>
> https://lore.kernel.org/r/cover.1794997749.git.lukas@wunner.de
>
> ...and so if/when that other series gets applied to pci/aer,
> the two patches will have to be applied once more as otherwise
> the last (7th) patch in that series doesn't apply cleanly.
>
> If on the other hand you move the patches from pci/portdrv to pci/aer,
> the first two patches in my series need not (and should not) be applied.
Thanks, I did move all these to pci/aer to avoid this complication.
There were minor conflicts with Yazen's patches in
sysfs-bus-pci-devices-aer but nothing serious, and if we rework the
negative value handling in the ratelimiting parameters they would
mostly disappear.
prev parent reply other threads:[~2026-11-20 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 18:17 [PATCH v3 0/6] PCI/DPC: Decide DPC ownership with host_bridge->native_dpc Kuppuswamy Sathyanarayanan
2026-11-18 18:17 ` [PATCH v3 1/6] PCI/DPC: Avoid access to non-existent AER capability Kuppuswamy Sathyanarayanan
2026-11-18 18:24 ` sashiko-bot
2026-11-18 18:17 ` [PATCH v3 2/6] PCI/DPC: Reinstate support for AER-incapable ports Kuppuswamy Sathyanarayanan
2026-11-18 18:24 ` sashiko-bot
2026-11-18 18:17 ` [PATCH v3 3/6] PCI/EDR: Build EDR whenever DPC is enabled on ACPI Kuppuswamy Sathyanarayanan
2026-11-18 18:24 ` sashiko-bot
2026-11-18 18:17 ` [PATCH v3 4/6] PCI/portdrv: Don't require AER to bind DPC service Kuppuswamy Sathyanarayanan
2026-11-18 18:26 ` sashiko-bot
2026-11-18 18:17 ` [PATCH v3 5/6] PCI/ACPI: Request DPC control only together with AER control Kuppuswamy Sathyanarayanan
2026-11-18 18:24 ` sashiko-bot
2026-11-18 18:17 ` [PATCH v3 6/6] PCI/portdrv: Bind DPC service based on host_bridge->native_dpc Kuppuswamy Sathyanarayanan
2026-11-18 18:24 ` sashiko-bot
2026-11-19 0:10 ` [PATCH v3 0/6] PCI/DPC: Decide DPC ownership with host_bridge->native_dpc Bjorn Helgaas
2026-11-19 9:28 ` Lukas Wunner
2026-11-20 18:18 ` Bjorn Helgaas [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=20261120181841.GA893187@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=yazen.ghannam@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.