From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Atharva Tiwari <evepolonium@gmail.com>
Cc: Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
<linuxppc-dev@lists.ozlabs.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI/ERR: use panic instead pci_info for device recovery failure in PCIe
Date: Fri, 3 Jan 2025 11:16:51 +0000 [thread overview]
Message-ID: <20250103111651.00007c57@huawei.com> (raw)
In-Reply-To: <20241227065253.72323-1-evepolonium@gmail.com>
On Fri, 27 Dec 2024 12:22:53 +0530
Atharva Tiwari <evepolonium@gmail.com> wrote:
> update failed in drivers/pci/pcie/err.c to
> trigger a kernel panic instead of pci_info
>
> Thanks
Rewrite message as described in submitting patches documentation.
Key thing here is question of 'why?'
A question was in that comment, what is your reasoning for panic being the
correct choice?
Jonathan
>
> Signed-off-by: Atharva Tiwari <evepolonium@gmail.com>
> ---
> drivers/pci/pcie/err.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pcie/err.c b/drivers/pci/pcie/err.c
> index 31090770fffc..2630b88564d8 100644
> --- a/drivers/pci/pcie/err.c
> +++ b/drivers/pci/pcie/err.c
> @@ -271,8 +271,8 @@ pci_ers_result_t pcie_do_recovery(struct pci_dev *dev,
>
> pci_uevent_ers(bridge, PCI_ERS_RESULT_DISCONNECT);
>
> - /* TODO: Should kernel panic here? */
> - pci_info(bridge, "device recovery failed\n");
> +
> + panic("Kernel Panic: %s: Device recovery failed\n", pci_name(bridge));
>
> return status;
> }
prev parent reply other threads:[~2025-01-03 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 6:52 [PATCH] PCI/ERR: use panic instead pci_info for device recovery failure in PCIe Atharva Tiwari
2025-01-03 11:16 ` Jonathan Cameron [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=20250103111651.00007c57@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=evepolonium@gmail.com \
--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 \
/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).