From: Joe Perches <joe@perches.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Benjamin Berg <bberg@redhat.com>,
linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Christian Kellner <ckellner@redhat.com>,
Tony Luck <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH] x86/mce: Lower throttling MCE messages to warnings
Date: Wed, 09 Oct 2019 11:44:00 -0700 [thread overview]
Message-ID: <cf1934f2668eea9d35dea1d16bb26cf911d4f831.camel@perches.com> (raw)
In-Reply-To: <20191009182246.GL10395@zn.tnic>
On Wed, 2019-10-09 at 20:22 +0200, Borislav Petkov wrote:
> On Wed, Oct 09, 2019 at 11:05:37AM -0700, Joe Perches wrote:
> > Perhaps this should be
> >
> > pr_warn_ratelimited(...)
> >
> > as the temperature changes can be relatively quick.
>
> There's already ratelimiting machinery a bit above in the same function.
right, thanks, nevermind...
next prev parent reply other threads:[~2019-10-09 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 15:54 [PATCH] x86/mce: Lower throttling MCE messages to warnings Benjamin Berg
2019-10-09 15:57 ` Hans de Goede
2019-10-09 17:56 ` Borislav Petkov
2019-10-09 18:05 ` Joe Perches
2019-10-09 18:22 ` Borislav Petkov
2019-10-09 18:44 ` Joe Perches [this message]
2019-10-10 21:08 ` Srinivas Pandruvada
2019-10-11 7:31 ` Benjamin Berg
2019-10-17 7:20 ` [tip: ras/core] x86/mce: Lower throttling MCE messages' priority to warning tip-bot2 for Benjamin Berg
[not found] <5da27a3e.1c69fb81.d3083.7f73SMTPIN_ADDED_BROKEN@mx.google.com>
2019-10-13 7:35 ` [PATCH] x86/mce: Lower throttling MCE messages to warnings Hans de Goede
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=cf1934f2668eea9d35dea1d16bb26cf911d4f831.camel@perches.com \
--to=joe@perches.com \
--cc=bberg@redhat.com \
--cc=bp@alien8.de \
--cc=ckellner@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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).