From: David Heidelberg <david@ixit.cz>
To: grundler@chromium.org
Cc: rajatja@chromium.org, rajat.khandelwal@linux.intel.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
mahesh@linux.ibm.com, oohall@gmail.com, bhelgaas@google.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO
Date: Sun, 13 Aug 2023 02:44:57 +0200 [thread overview]
Message-ID: <4fa1e0fe-eec4-4e5c-8acd-274a039c048a@ixit.cz> (raw)
In-Reply-To: <20230606035442.2886343-1-grundler@chromium.org>
Tested-by: David Heidelberg <david@ixit.cz>
For PATCH v4 please fix the typo reported by the bot :)
Seeing messages as
__aer_print_error: 72 callbacks suppressed
but it still prints many errors on my laptop. Anyway, the log is less
filled with this patch, so great!
Thank you
David
--
David Heidelberg
Certified Linux Magician
next prev parent reply other threads:[~2023-08-13 0:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 3:54 [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO Grant Grundler
2023-06-06 3:54 ` [PATCHv3 pci-next 2/2] PCI/AER: Rate limit the reporting of the correctable errors Grant Grundler
2023-06-06 7:21 ` kernel test robot
2023-06-06 9:49 ` kernel test robot
2023-08-13 0:44 ` David Heidelberg [this message]
2023-08-14 15:40 ` [PATCHv3 pci-next 1/2] PCI/AER: correctable error message as KERN_INFO Grant Grundler
2023-09-18 11:42 ` Xi Ruoyao
2023-09-18 18:33 ` Grant Grundler
2023-09-18 19:39 ` Bjorn Helgaas
2024-03-24 17:19 ` Xi Ruoyao
2024-03-25 8:45 ` Ethan Zhao
2024-03-25 10:15 ` Xi Ruoyao
2024-03-25 21:40 ` Xi Ruoyao
2024-03-26 1:39 ` Ethan Zhao
2024-03-26 21:17 ` Bjorn Helgaas
2024-03-27 3:49 ` Ethan Zhao
2024-04-02 0:27 ` Xi Ruoyao
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=4fa1e0fe-eec4-4e5c-8acd-274a039c048a@ixit.cz \
--to=david@ixit.cz \
--cc=20230606035442.2886343-1-grundler@chromium.org \
--cc=bhelgaas@google.com \
--cc=grundler@chromium.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=rajat.khandelwal@linux.intel.com \
--cc=rajatja@chromium.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;
as well as URLs for NNTP newsgroup(s).