Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org
Cc: dave@stgolabs.net, jic23@kernel.org, alison.schofield@intel.com,
	djbw@kernel.org
Subject: [PATCH 0/2] cxl/pci: Fix the incorrect check of pci_config_read/write*() returns
Date: Wed,  3 Jun 2026 11:57:50 -0700	[thread overview]
Message-ID: <20260603185752.4149725-1-dave.jiang@intel.com> (raw)

The patches are inspired by comments from Richard Cheng WRT pci config
accessors return PCIBIOS errors that are positive integers rather than
negative errnos. I went and audited the cxl PCI code and found a few
locations that need to be fixed. There are other locations that may
trigger issues, but at this point we'll fix them as they happen.


Dave Jiang (2):
  cxl/pci: Fix the incorrect check of pci_read_config_word() return
  cxl/pci: Convert PCIBIOS errors to errno on DVSEC config accesses

 drivers/cxl/core/pci.c | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)


base-commit: e43ffb69e0438cddd72aaa30898b4dc446f664f8
-- 
2.54.0


             reply	other threads:[~2026-06-03 18:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 18:57 Dave Jiang [this message]
2026-06-03 18:57 ` [PATCH 1/2] cxl/pci: Fix the incorrect check of pci_read_config_word() return Dave Jiang
2026-06-04 10:45   ` Richard Cheng
2026-06-04 16:17   ` Alison Schofield
2026-06-03 18:57 ` [PATCH 2/2] cxl/pci: Convert PCIBIOS errors to errno on DVSEC config accesses Dave Jiang
2026-06-04 10:45   ` Richard Cheng
2026-06-04 16:46   ` Alison Schofield
2026-06-04 10:17 ` [PATCH 0/2] cxl/pci: Fix the incorrect check of pci_config_read/write*() returns Jonathan Cameron
2026-06-04 10:30   ` Richard Cheng
2026-06-04 10:51     ` Richard Cheng
2026-06-04 15:58       ` Dave Jiang
2026-06-04 16:10         ` Dave Jiang
2026-06-04 15:57     ` Dave Jiang
2026-06-04 16:19 ` Alison Schofield

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=20260603185752.4149725-1-dave.jiang@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    /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