From: Bjorn Helgaas <helgaas@kernel.org>
To: Naveen Naidu <naveennaidu479@gmail.com>
Cc: bhelgaas@google.com, "Krzysztof Wilczyński" <kw@linux.com>,
linux-hyperv@vger.kernel.org, "Heiko Stuebner" <heiko@sntech.de>,
linux-pci@vger.kernel.org, "Shawn Lin" <shawn.lin@rock-chips.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Kuppuswamy Sathyanarayanan"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Russell Currey" <ruscur@russell.cc>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Toan Le" <toan@os.amperecomputing.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Rob Herring" <robh@kernel.org>, "Wei Liu" <wei.liu@kernel.org>,
linux-samsung-soc@vger.kernel.org,
"Marc Zyngier" <maz@kernel.org>,
"Joyce Ooi" <joyce.ooi@intel.com>,
"Dexuan Cui" <decui@microsoft.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
linux-rockchip@lists.infradead.org,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>,
"Xiaowei Song" <songxiaowei@hisilicon.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
"Robert Richter" <rric@kernel.org>,
"Sean V Kelley" <sean.v.kelley@intel.com>,
"Ray Jui" <rjui@broadcom.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Ryder Lee" <ryder.lee@mediatek.com>,
linux-mediatek@lists.infradead.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
linux-arm-kernel@lists.infradead.org,
"Qiuxu Zhuo" <qiuxu.zhuo@intel.com>,
"Scott Branden" <sbranden@broadcom.com>,
linuxppc-dev@lists.ozlabs.org,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Lukas Wunner" <lukas@wunner.de>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH v4 00/25] Unify PCI error response checking
Date: Thu, 18 Nov 2021 14:44:21 -0600 [thread overview]
Message-ID: <20211118204421.GA1881943@bhelgaas> (raw)
In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com>
On Thu, Nov 18, 2021 at 07:33:10PM +0530, Naveen Naidu wrote:
> An MMIO read from a PCI device that doesn't exist or doesn't respond
> causes a PCI error. There's no real data to return to satisfy the
> CPU read, so most hardware fabricates ~0 data.
>
> This patch series adds PCI_ERROR_RESPONSE definition and other helper
> definition PCI_SET_ERROR_RESPONSE and PCI_POSSIBLE_ERROR and uses it
> where appropriate to make these checks consistent and easier to find.
>
> This helps unify PCI error response checking and make error check
> consistent and easier to find.
>
> This series also ensures that the error response fabrication now happens
> in the PCI_OP_READ and PCI_USER_READ_CONFIG. This removes the
> responsibility from controller drivers to do the error response setting.
Applied to pci/error for v5.17. Thanks, this is really nice work.
Somehow small changes like these add up to something much greater than
one would expect.
This touches many native controller drivers but in trivial ways, so I
plan to merge this branch after the usual native controller stuff from
Lorenzo.
I tweaked the commit logs to clarify that this series is all about
*config* reads, not MMIO reads. MMIO reads have similar issues, and
we can use PCI_ERROR_RESPONSE, etc., there, too, but that's not what
this series does.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Naveen Naidu <naveennaidu479@gmail.com>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
linux-hyperv@vger.kernel.org, "Heiko Stuebner" <heiko@sntech.de>,
linux-pci@vger.kernel.org, "Shawn Lin" <shawn.lin@rock-chips.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Kuppuswamy Sathyanarayanan"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"Ryder Lee" <ryder.lee@mediatek.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Toan Le" <toan@os.amperecomputing.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Rob Herring" <robh@kernel.org>, "Wei Liu" <wei.liu@kernel.org>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Marc Zyngier" <maz@kernel.org>,
"Dexuan Cui" <decui@microsoft.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
linux-rockchip@lists.infradead.org,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>,
"Xiaowei Song" <songxiaowei@hisilicon.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Robert Richter" <rric@kernel.org>,
"Sean V Kelley" <sean.v.kelley@intel.com>,
"Ray Jui" <rjui@broadcom.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
linux-samsung-soc@vger.kernel.org,
linux-mediatek@lists.infradead.org, bhelgaas@google.com,
linux-arm-kernel@lists.infradead.org,
"Qiuxu Zhuo" <qiuxu.zhuo@intel.com>,
"Pali Rohár" <pali@kernel.org>,
"Scott Branden" <sbranden@broadcom.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Lukas Wunner" <lukas@wunner.de>,
"Joyce Ooi" <joyce.ooi@intel.com>,
"Shawn Guo" <shawn.guo@linaro.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 00/25] Unify PCI error response checking
Date: Thu, 18 Nov 2021 14:44:21 -0600 [thread overview]
Message-ID: <20211118204421.GA1881943@bhelgaas> (raw)
In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com>
On Thu, Nov 18, 2021 at 07:33:10PM +0530, Naveen Naidu wrote:
> An MMIO read from a PCI device that doesn't exist or doesn't respond
> causes a PCI error. There's no real data to return to satisfy the
> CPU read, so most hardware fabricates ~0 data.
>
> This patch series adds PCI_ERROR_RESPONSE definition and other helper
> definition PCI_SET_ERROR_RESPONSE and PCI_POSSIBLE_ERROR and uses it
> where appropriate to make these checks consistent and easier to find.
>
> This helps unify PCI error response checking and make error check
> consistent and easier to find.
>
> This series also ensures that the error response fabrication now happens
> in the PCI_OP_READ and PCI_USER_READ_CONFIG. This removes the
> responsibility from controller drivers to do the error response setting.
Applied to pci/error for v5.17. Thanks, this is really nice work.
Somehow small changes like these add up to something much greater than
one would expect.
This touches many native controller drivers but in trivial ways, so I
plan to merge this branch after the usual native controller stuff from
Lorenzo.
I tweaked the commit logs to clarify that this series is all about
*config* reads, not MMIO reads. MMIO reads have similar issues, and
we can use PCI_ERROR_RESPONSE, etc., there, too, but that's not what
this series does.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Naveen Naidu <naveennaidu479@gmail.com>
Cc: bhelgaas@google.com, "Krzysztof Wilczyński" <kw@linux.com>,
linux-hyperv@vger.kernel.org, "Heiko Stuebner" <heiko@sntech.de>,
linux-pci@vger.kernel.org, "Shawn Lin" <shawn.lin@rock-chips.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Kuppuswamy Sathyanarayanan"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Russell Currey" <ruscur@russell.cc>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Toan Le" <toan@os.amperecomputing.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Rob Herring" <robh@kernel.org>, "Wei Liu" <wei.liu@kernel.org>,
linux-samsung-soc@vger.kernel.org,
"Marc Zyngier" <maz@kernel.org>,
"Joyce Ooi" <joyce.ooi@intel.com>,
"Dexuan Cui" <decui@microsoft.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
linux-rockchip@lists.infradead.org,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>,
"Xiaowei Song" <songxiaowei@hisilicon.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
"Robert Richter" <rric@kernel.org>,
"Sean V Kelley" <sean.v.kelley@intel.com>,
"Ray Jui" <rjui@broadcom.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Ryder Lee" <ryder.lee@mediatek.com>,
linux-mediatek@lists.infradead.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
linux-arm-kernel@lists.infradead.org,
"Qiuxu Zhuo" <qiuxu.zhuo@intel.com>,
"Scott Branden" <sbranden@broadcom.com>,
linuxppc-dev@lists.ozlabs.org,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Lukas Wunner" <lukas@wunner.de>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH v4 00/25] Unify PCI error response checking
Date: Thu, 18 Nov 2021 14:44:21 -0600 [thread overview]
Message-ID: <20211118204421.GA1881943@bhelgaas> (raw)
In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com>
On Thu, Nov 18, 2021 at 07:33:10PM +0530, Naveen Naidu wrote:
> An MMIO read from a PCI device that doesn't exist or doesn't respond
> causes a PCI error. There's no real data to return to satisfy the
> CPU read, so most hardware fabricates ~0 data.
>
> This patch series adds PCI_ERROR_RESPONSE definition and other helper
> definition PCI_SET_ERROR_RESPONSE and PCI_POSSIBLE_ERROR and uses it
> where appropriate to make these checks consistent and easier to find.
>
> This helps unify PCI error response checking and make error check
> consistent and easier to find.
>
> This series also ensures that the error response fabrication now happens
> in the PCI_OP_READ and PCI_USER_READ_CONFIG. This removes the
> responsibility from controller drivers to do the error response setting.
Applied to pci/error for v5.17. Thanks, this is really nice work.
Somehow small changes like these add up to something much greater than
one would expect.
This touches many native controller drivers but in trivial ways, so I
plan to merge this branch after the usual native controller stuff from
Lorenzo.
I tweaked the commit logs to clarify that this series is all about
*config* reads, not MMIO reads. MMIO reads have similar issues, and
we can use PCI_ERROR_RESPONSE, etc., there, too, but that's not what
this series does.
Bjorn
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Naveen Naidu <naveennaidu479@gmail.com>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
linux-hyperv@vger.kernel.org, "Heiko Stuebner" <heiko@sntech.de>,
linux-pci@vger.kernel.org, "Shawn Lin" <shawn.lin@rock-chips.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Kuppuswamy Sathyanarayanan"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"Ryder Lee" <ryder.lee@mediatek.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Russell Currey" <ruscur@russell.cc>,
"Toan Le" <toan@os.amperecomputing.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Rob Herring" <robh@kernel.org>, "Wei Liu" <wei.liu@kernel.org>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Marc Zyngier" <maz@kernel.org>,
"Dexuan Cui" <decui@microsoft.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
linux-rockchip@lists.infradead.org,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>,
"Xiaowei Song" <songxiaowei@hisilicon.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Robert Richter" <rric@kernel.org>,
"Sean V Kelley" <sean.v.kelley@intel.com>,
"Ray Jui" <rjui@broadcom.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
linux-samsung-soc@vger.kernel.org,
linux-mediatek@lists.infradead.org, bhelgaas@google.com,
linux-arm-kernel@lists.infradead.org,
"Qiuxu Zhuo" <qiuxu.zhuo@intel.com>,
"Pali Rohár" <pali@kernel.org>,
"Scott Branden" <sbranden@broadcom.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Lukas Wunner" <lukas@wunner.de>,
"Joyce Ooi" <joyce.ooi@intel.com>,
"Shawn Guo" <shawn.guo@linaro.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 00/25] Unify PCI error response checking
Date: Thu, 18 Nov 2021 14:44:21 -0600 [thread overview]
Message-ID: <20211118204421.GA1881943@bhelgaas> (raw)
In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com>
On Thu, Nov 18, 2021 at 07:33:10PM +0530, Naveen Naidu wrote:
> An MMIO read from a PCI device that doesn't exist or doesn't respond
> causes a PCI error. There's no real data to return to satisfy the
> CPU read, so most hardware fabricates ~0 data.
>
> This patch series adds PCI_ERROR_RESPONSE definition and other helper
> definition PCI_SET_ERROR_RESPONSE and PCI_POSSIBLE_ERROR and uses it
> where appropriate to make these checks consistent and easier to find.
>
> This helps unify PCI error response checking and make error check
> consistent and easier to find.
>
> This series also ensures that the error response fabrication now happens
> in the PCI_OP_READ and PCI_USER_READ_CONFIG. This removes the
> responsibility from controller drivers to do the error response setting.
Applied to pci/error for v5.17. Thanks, this is really nice work.
Somehow small changes like these add up to something much greater than
one would expect.
This touches many native controller drivers but in trivial ways, so I
plan to merge this branch after the usual native controller stuff from
Lorenzo.
I tweaked the commit logs to clarify that this series is all about
*config* reads, not MMIO reads. MMIO reads have similar issues, and
we can use PCI_ERROR_RESPONSE, etc., there, too, but that's not what
this series does.
Bjorn
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Naveen Naidu <naveennaidu479@gmail.com>
Cc: bhelgaas@google.com, "Krzysztof Wilczyński" <kw@linux.com>,
linux-hyperv@vger.kernel.org, "Heiko Stuebner" <heiko@sntech.de>,
linux-pci@vger.kernel.org, "Shawn Lin" <shawn.lin@rock-chips.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Kuppuswamy Sathyanarayanan"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Russell Currey" <ruscur@russell.cc>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Toan Le" <toan@os.amperecomputing.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Rob Herring" <robh@kernel.org>, "Wei Liu" <wei.liu@kernel.org>,
linux-samsung-soc@vger.kernel.org,
"Marc Zyngier" <maz@kernel.org>,
"Joyce Ooi" <joyce.ooi@intel.com>,
"Dexuan Cui" <decui@microsoft.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
linux-rockchip@lists.infradead.org,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>,
"Xiaowei Song" <songxiaowei@hisilicon.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
"Robert Richter" <rric@kernel.org>,
"Sean V Kelley" <sean.v.kelley@intel.com>,
"Ray Jui" <rjui@broadcom.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Ryder Lee" <ryder.lee@mediatek.com>,
linux-mediatek@lists.infradead.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
linux-arm-kernel@lists.infradead.org,
"Qiuxu Zhuo" <qiuxu.zhuo@intel.com>,
"Scott Branden" <sbranden@broadcom.com>,
linuxppc-dev@lists.ozlabs.org,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Lukas Wunner" <lukas@wunner.de>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH v4 00/25] Unify PCI error response checking
Date: Thu, 18 Nov 2021 14:44:21 -0600 [thread overview]
Message-ID: <20211118204421.GA1881943@bhelgaas> (raw)
In-Reply-To: <cover.1637243717.git.naveennaidu479@gmail.com>
On Thu, Nov 18, 2021 at 07:33:10PM +0530, Naveen Naidu wrote:
> An MMIO read from a PCI device that doesn't exist or doesn't respond
> causes a PCI error. There's no real data to return to satisfy the
> CPU read, so most hardware fabricates ~0 data.
>
> This patch series adds PCI_ERROR_RESPONSE definition and other helper
> definition PCI_SET_ERROR_RESPONSE and PCI_POSSIBLE_ERROR and uses it
> where appropriate to make these checks consistent and easier to find.
>
> This helps unify PCI error response checking and make error check
> consistent and easier to find.
>
> This series also ensures that the error response fabrication now happens
> in the PCI_OP_READ and PCI_USER_READ_CONFIG. This removes the
> responsibility from controller drivers to do the error response setting.
Applied to pci/error for v5.17. Thanks, this is really nice work.
Somehow small changes like these add up to something much greater than
one would expect.
This touches many native controller drivers but in trivial ways, so I
plan to merge this branch after the usual native controller stuff from
Lorenzo.
I tweaked the commit logs to clarify that this series is all about
*config* reads, not MMIO reads. MMIO reads have similar issues, and
we can use PCI_ERROR_RESPONSE, etc., there, too, but that's not what
this series does.
Bjorn
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2021-11-18 20:44 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 14:03 [PATCH v4 00/25] Unify PCI error response checking Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 01/25] PCI: Add PCI_ERROR_RESPONSE and it's related definitions Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 02/25] PCI: Set error response in config access defines when ops->read() fails Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 03/25] PCI: Use PCI_SET_ERROR_RESPONSE() when device not found Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 04/25] PCI: Remove redundant error fabrication when device read fails Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 05/25] PCI: thunder: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 06/25] PCI: iproc: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 07/25] PCI: mediatek: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 08/25] PCI: exynos: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 09/25] PCI: histb: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 10/25] PCI: kirin: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 11/25] PCI: aardvark: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 12/25] PCI: mvebu: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 13/25] PCI: altera: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 14/25] PCI: rcar: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 15/25] PCI: rockchip: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 16/25] PCI/ERR: Use PCI_POSSIBLE_ERROR() to check read from hardware Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 17/25] PCI: vmd: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 18/25] PCI: pciehp: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 19/25] PCI/DPC: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 20/25] PCI/PME: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 21/25] PCI: cpqphp: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 22/25] PCI: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 23/25] PCI: keystone: " Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 24/25] PCI: hv: Use PCI_ERROR_RESPONSE to specify hardware read error Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` [PATCH v4 25/25] PCI: xgene: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 14:03 ` Naveen Naidu
2021-11-18 20:44 ` Bjorn Helgaas [this message]
2021-11-18 20:44 ` [PATCH v4 00/25] Unify PCI error response checking Bjorn Helgaas
2021-11-18 20:44 ` Bjorn Helgaas
2021-11-18 20:44 ` Bjorn Helgaas
2021-11-18 20:44 ` Bjorn Helgaas
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=20211118204421.GA1881943@bhelgaas \
--to=helgaas@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=heiko@sntech.de \
--cc=jianjun.wang@mediatek.com \
--cc=jingoohan1@gmail.com \
--cc=jonathan.derrick@linux.dev \
--cc=joyce.ooi@intel.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.de \
--cc=marek.vasut+renesas@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=naveennaidu479@gmail.com \
--cc=nirmal.patel@linux.intel.com \
--cc=oohall@gmail.com \
--cc=pali@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=rric@kernel.org \
--cc=ruscur@russell.cc \
--cc=ryder.lee@mediatek.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sbranden@broadcom.com \
--cc=sean.v.kelley@intel.com \
--cc=shawn.guo@linaro.org \
--cc=shawn.lin@rock-chips.com \
--cc=songxiaowei@hisilicon.com \
--cc=sthemmin@microsoft.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=toan@os.amperecomputing.com \
--cc=wangbinghui@hisilicon.com \
--cc=wei.liu@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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.