From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, bhelgaas@google.com,
kbusch@kernel.org
Cc: mahesh@linux.ibm.com, oohall@gmail.com,
Jonathan.Cameron@huawei.com, terry.bowman@amd.com
Subject: Re: [PATCH v3 1/4] PCI/DPC: Rename pdev to err_port for dpc_handler
Date: Tue, 11 Feb 2025 13:17:55 -0800 [thread overview]
Message-ID: <f4d2579c-97ab-41d7-a496-7c711243517f@linux.intel.com> (raw)
In-Reply-To: <20250207093500.70885-2-xueshuai@linux.alibaba.com>
On 2/7/25 1:34 AM, Shuai Xue wrote:
> The irq handler is registered for error port which recevie DPC
> interrupt. Rename pdev to err_port.
>
> No functional changes.
>
> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>
> ---
I think you can combine patch 1 & 2 into a single patch. Change wise, it
looks
fine to me.
Reviewed-by: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
> drivers/pci/pcie/dpc.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pci/pcie/dpc.c b/drivers/pci/pcie/dpc.c
> index 242cabd5eeeb..1a54a0b657ae 100644
> --- a/drivers/pci/pcie/dpc.c
> +++ b/drivers/pci/pcie/dpc.c
> @@ -346,21 +346,21 @@ static bool dpc_is_surprise_removal(struct pci_dev *pdev)
>
> static irqreturn_t dpc_handler(int irq, void *context)
> {
> - struct pci_dev *pdev = context;
> + struct pci_dev *err_port = context;
>
> /*
> * According to PCIe r6.0 sec 6.7.6, errors are an expected side effect
> * of async removal and should be ignored by software.
> */
> - if (dpc_is_surprise_removal(pdev)) {
> - dpc_handle_surprise_removal(pdev);
> + if (dpc_is_surprise_removal(err_port)) {
> + dpc_handle_surprise_removal(err_port);
> return IRQ_HANDLED;
> }
>
> - dpc_process_error(pdev);
> + dpc_process_error(err_port);
>
> /* We configure DPC so it only triggers on ERR_FATAL */
> - pcie_do_recovery(pdev, pci_channel_io_frozen, dpc_reset_link);
> + pcie_do_recovery(err_port, pci_channel_io_frozen, dpc_reset_link);
>
> return IRQ_HANDLED;
> }
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2025-02-11 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 9:34 [PATCH v3 0/4] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2025-02-07 9:34 ` [PATCH v3 1/4] PCI/DPC: Rename pdev to err_port for dpc_handler Shuai Xue
2025-02-11 21:17 ` Sathyanarayanan Kuppuswamy [this message]
2025-02-12 2:47 ` Shuai Xue
2025-02-07 9:34 ` [PATCH v3 2/4] PCI/EDR: Rename edev to err_port for edr_handle_event Shuai Xue
2025-02-07 9:34 ` [PATCH v3 3/4] PCI/DPC: Run recovery on device that detected the error Shuai Xue
2025-02-11 21:23 ` Sathyanarayanan Kuppuswamy
2025-02-12 5:51 ` Shuai Xue
2025-02-07 9:35 ` [PATCH v3 4/4] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
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=f4d2579c-97ab-41d7-a496-7c711243517f@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=terry.bowman@amd.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;
as well as URLs for NNTP newsgroup(s).