From: "Luck, Tony" <tony.luck@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"kernelorg@undead.fr" <kernelorg@undead.fr>,
"kjhambrick@gmail.com" <kjhambrick@gmail.com>,
"2lprbe78@duck.com" <2lprbe78@duck.com>,
"nicholas.johnson-opensource@outlook.com.au"
<nicholas.johnson-opensource@outlook.com.au>,
"benoitg@coeus.ca" <benoitg@coeus.ca>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"wse@tuxedocomputers.com" <wse@tuxedocomputers.com>,
"mumblingdrunkard@protonmail.com"
<mumblingdrunkard@protonmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Box, David E" <david.e.box@intel.com>,
"Sun, Yunying" <yunying.sun@intel.com>
Subject: RE: Bug report: the extended PCI config space is missed with 6.2-rc2
Date: Thu, 5 Jan 2023 21:49:44 +0000 [thread overview]
Message-ID: <SJ1PR11MB608376AF8369BE02661C48D7FCFA9@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230105203757.GA1166631@bhelgaas>
> The EDAC driver wouldn't have any ACPI stuff in it; it's just that
> Linux is looking for ACPI info about the ECAM area.
Is there some way for a driver to know that pci_read_config_dword()
is going to fail for offsets in extended PCIe config space?
-Tony
next prev parent reply other threads:[~2023-01-05 21:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ1PR11MB6083C504335B2DE1B31C440CFCFA9@SJ1PR11MB6083.namprd11.prod.outlook.com>
2023-01-05 18:29 ` Bug report: the extended PCI config space is missed with 6.2-rc2 Bjorn Helgaas
2023-01-05 19:23 ` Liang, Kan
2023-01-05 19:44 ` Bjorn Helgaas
2023-01-05 19:44 ` Dan Williams
2023-01-05 19:58 ` Luck, Tony
2023-01-05 20:37 ` Bjorn Helgaas
2023-01-05 21:49 ` Luck, Tony [this message]
2023-01-05 22:20 ` Bjorn Helgaas
2023-01-05 20:23 ` Bjorn Helgaas
2023-01-05 21:20 ` Dan Williams
2023-01-05 21:35 ` Bjorn Helgaas
2023-01-05 21:43 ` Dan Williams
2023-01-05 21:48 ` Bjorn Helgaas
2023-01-04 14:39 Liang, Kan
2023-01-04 14:50 ` Bjorn Helgaas
2023-01-04 15:45 ` Bjorn Helgaas
2023-01-05 17:42 ` Tony Luck
2023-01-05 17:51 ` Bjorn Helgaas
2023-01-05 22:32 ` Bjorn Helgaas
2023-01-05 23:38 ` Dan Williams
2023-01-06 0:22 ` Luck, Tony
2023-01-06 0:47 ` Bjorn Helgaas
2023-01-06 17:33 ` Bjorn Helgaas
2023-01-06 18:03 ` Luck, Tony
2023-01-06 20:52 ` Bjorn Helgaas
2023-01-06 21:37 ` Luck, Tony
2023-01-06 22:04 ` Bjorn Helgaas
2023-01-06 22:30 ` Luck, Tony
2023-01-10 5:43 ` Sun, Yunying
2023-01-10 18:12 ` Rafael J. Wysocki
2023-01-10 19:06 ` Bjorn Helgaas
2023-01-06 0:32 ` Bjorn Helgaas
2023-01-06 0:50 ` Liang, Kan
2023-01-09 12:27 ` Giovanni Cabiddu
2023-01-06 9:44 ` Linux kernel regression tracking (#adding)
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=SJ1PR11MB608376AF8369BE02661C48D7FCFA9@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=2lprbe78@duck.com \
--cc=benoitg@coeus.ca \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=david.e.box@intel.com \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kernelorg@undead.fr \
--cc=kjhambrick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mumblingdrunkard@protonmail.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=wse@tuxedocomputers.com \
--cc=yunying.sun@intel.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;
as well as URLs for NNTP newsgroup(s).