From: Borislav Petkov <bp@alien8.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-edac@vger.kernel.org, tony.luck@intel.com,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
kernel-team@fb.com
Subject: Re: [PATCH RFC x86/mce] Make mce_timed_out() identify holdout CPUs
Date: Fri, 8 Jan 2021 17:57:48 +0100 [thread overview]
Message-ID: <20210108165748.GE4042@zn.tnic> (raw)
In-Reply-To: <20210108145514.GS2743@paulmck-ThinkPad-P72>
On Fri, Jan 08, 2021 at 06:55:14AM -0800, Paul E. McKenney wrote:
> Looks good to me! I agree that your change to the pr_emerg() string is
> much better than my original.
Well, the rest of the MCE code uses pr_emerg on that path so...
> And good point on your added comment, plus it was fun to see that my
> original "holdouts" wording has not completely vanished. ;-)
I had to leave it in seeing how you love that formulation. :-P
> Thank you very much!!!
Thanks too Paul!
/me queues.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-01-08 16:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 17:41 [PATCH RFC x86/mce] Make mce_timed_out() identify holdout CPUs Paul E. McKenney
2021-01-06 18:32 ` Borislav Petkov
2021-01-06 19:13 ` Paul E. McKenney
2021-01-07 7:07 ` Borislav Petkov
2021-01-07 17:08 ` Paul E. McKenney
2021-01-08 12:31 ` Borislav Petkov
2021-01-08 14:55 ` Paul E. McKenney
2021-01-08 16:57 ` Borislav Petkov [this message]
2021-01-06 18:39 ` Luck, Tony
2021-01-06 19:17 ` Paul E. McKenney
2021-01-06 22:49 ` Luck, Tony
2021-01-06 23:23 ` Paul E. McKenney
2021-01-07 0:26 ` Luck, Tony
2021-01-07 0:41 ` Paul E. McKenney
2021-01-08 17:09 ` [tip: ras/core] x86/mce: " tip-bot2 for Paul E. McKenney
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=20210108165748.GE4042@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kernel-team@fb.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--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