From: Joe Perches <joe@perches.com>
To: Abhinav Jain <jain.abhinav177@gmail.com>,
mahesh@linux.ibm.com, oohall@gmail.com, bhelgaas@google.com,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: skhan@linuxfoundation.org, javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH] PCI/AER: Print error message as per the TODO
Date: Mon, 15 Apr 2024 09:19:59 -0700 [thread overview]
Message-ID: <03f357e6c16d13924b705513446e4eac37e38a99.camel@perches.com> (raw)
In-Reply-To: <20240415161055.8316-1-jain.abhinav177@gmail.com>
On Mon, 2024-04-15 at 16:10 +0000, Abhinav Jain wrote:
> Add a pr_err() to print the add device error in find_device_iter()
[]
> diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c
[]
> @@ -885,7 +885,8 @@ static int find_device_iter(struct pci_dev *dev, void *data)
> /* List this device */
> if (add_error_device(e_info, dev)) {
> /* We cannot handle more... Stop iteration */
> - /* TODO: Should print error message here? */
> + pr_err("find_device_iter: Cannot handle more devices.
> + Stopping iteration");
You are adding unnecessary whitespace after the period.
String concatenation keeps _all_ the whitespace.
The format is fine on a single line too.
Something like:
pr_notice("%s: Cannot handle more devices - iteration stopped\n",
__func__);
next prev parent reply other threads:[~2024-04-15 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 16:10 [PATCH] PCI/AER: Print error message as per the TODO Abhinav Jain
2024-04-15 16:19 ` Joe Perches [this message]
2024-06-05 21:23 ` [PATCH v2] " Abhinav Jain
2024-06-05 21:58 ` Bjorn Helgaas
2024-06-05 23:11 ` Abhinav Jain
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=03f357e6c16d13924b705513446e4eac37e38a99.camel@perches.com \
--to=joe@perches.com \
--cc=bhelgaas@google.com \
--cc=jain.abhinav177@gmail.com \
--cc=javier.carrasco.cruz@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 \
--cc=skhan@linuxfoundation.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