From: Hans de Goede <hdegoede@redhat.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
markgross@kernel.org
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: ISST: Reduce noise for missing numa information in logs
Date: Wed, 9 Aug 2023 22:01:44 +0200 [thread overview]
Message-ID: <aa35b6e9-e58e-de92-9a86-c5a9be13fd26@redhat.com> (raw)
In-Reply-To: <20230808174359.50602-1-srinivas.pandruvada@linux.intel.com>
Hi,
On 8/8/23 19:43, Srinivas Pandruvada wrote:
> On platforms with no numa support and with several CPUs, logs have lots
> of noise for message "Fail to get numa node for CPU:.."
>
> Change pr_info() to pr_info_once() as one print is enough to show the
> issue.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Thank you for your patch, I've applied this patch to my fixes
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=fixes
Note it will show up in my fixes branch once I've pushed my
local branch there, which might take a while.
I will include this patch in my next fixes pull-req to Linus
for the current kernel development cycle.
Regards,
Hans
> ---
> drivers/platform/x86/intel/speed_select_if/isst_if_common.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/speed_select_if/isst_if_common.c b/drivers/platform/x86/intel/speed_select_if/isst_if_common.c
> index 1f59ac55c5f7..a95004e3d80b 100644
> --- a/drivers/platform/x86/intel/speed_select_if/isst_if_common.c
> +++ b/drivers/platform/x86/intel/speed_select_if/isst_if_common.c
> @@ -335,8 +335,8 @@ static struct pci_dev *_isst_if_get_pci_dev(int cpu, int bus_no, int dev, int fn
>
> node = dev_to_node(&_pci_dev->dev);
> if (node == NUMA_NO_NODE) {
> - pr_info("Fail to get numa node for CPU:%d bus:%d dev:%d fn:%d\n",
> - cpu, bus_no, dev, fn);
> + pr_info_once("Fail to get numa node for CPU:%d bus:%d dev:%d fn:%d\n",
> + cpu, bus_no, dev, fn);
> continue;
> }
>
prev parent reply other threads:[~2023-08-09 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 17:43 Srinivas Pandruvada
2023-08-09 20:01 ` Hans de Goede [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=aa35b6e9-e58e-de92-9a86-c5a9be13fd26@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.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
all inboxes | Powered by JetHome®