From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Krishna chaitanya chundru <quic_krichai@quicinc.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] perf/dwc_pcie: Qualify RAS DES VSEC Capability by Vendor, Revision
Date: Wed, 11 Dec 2024 23:44:16 +0000 [thread overview]
Message-ID: <173395359744.1069392.3564048634010264629.b4-ty@kernel.org> (raw)
In-Reply-To: <20241209222938.3219364-1-helgaas@kernel.org>
On Mon, 09 Dec 2024 16:29:38 -0600, Bjorn Helgaas wrote:
> PCI Vendor-Specific (VSEC) Capabilities are defined by each vendor.
> Devices from different vendors may advertise a VSEC Capability with the DWC
> RAS DES functionality, but the vendors may assign different VSEC IDs.
>
> Search for the DWC RAS DES Capability using the VSEC ID and VSEC Rev
> chosen by the vendor.
>
> [...]
Thanks, Bjorn, for sorting this out and also to Shuai and Ilkka for
giving it a whirl on their platforms.
Applied to will (for-next/perf), thanks!
[1/1] perf/dwc_pcie: Qualify RAS DES VSEC Capability by Vendor, Revision
https://git.kernel.org/will/c/b34d605d120f
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-12-11 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 22:29 [PATCH] perf/dwc_pcie: Qualify RAS DES VSEC Capability by Vendor, Revision Bjorn Helgaas
2024-12-10 12:04 ` Shuai Xue
2024-12-10 14:53 ` Bjorn Helgaas
2024-12-11 1:24 ` Shuai Xue
2024-12-11 0:55 ` Ilkka Koskinen
2024-12-11 23:44 ` Will Deacon [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=173395359744.1069392.3564048634010264629.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=helgaas@kernel.org \
--cc=ilkka@os.amperecomputing.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=quic_krichai@quicinc.com \
--cc=xueshuai@linux.alibaba.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