From: Borislav Petkov <bp@alien8.de>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] mce: fix missing stack-dumping in mce_panic()
Date: Thu, 29 Dec 2022 13:51:33 +0100 [thread overview]
Message-ID: <Y62NVThhnGtnj71u@zn.tnic> (raw)
In-Reply-To: <1e97c11d-99b6-c06f-b67f-c56ba6653d27@huawei.com>
On Thu, Dec 29, 2022 at 08:33:55PM +0800, Miaohe Lin wrote:
> I think
You think or you know?
I'm assuming reverting 6e6f0a1f0fa6 shows the MCE panic?
I guess the original issue that commit was fixing is to save that
redundant oops message but Tony seems to want to see it now and I'm not
sure how much we care about 80x50 screens nowadays... :-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-12-29 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 16:37 Miaohe Lin
2022-12-02 14:44 ` Luck, Tony
2022-12-03 2:19 ` Miaohe Lin
2022-12-03 4:22 ` Tony Luck
2022-12-03 6:48 ` Miaohe Lin
2022-12-29 11:54 ` Borislav Petkov
2022-12-29 12:33 ` Miaohe Lin
2022-12-29 12:51 ` Borislav Petkov [this message]
2022-12-30 1:56 ` Miaohe Lin
2023-01-03 21:12 ` Luck, Tony
2023-01-06 1:57 ` Miaohe Lin
2023-01-06 17:42 ` Luck, Tony
2023-01-07 2:27 ` Miaohe Lin
2023-01-08 17:54 ` Luck, Tony
2023-01-09 2:16 ` Miaohe Lin
2023-01-09 4:45 ` Luck, Tony
2023-01-09 6:54 ` Miaohe Lin
2022-12-10 2:28 ` Miaohe Lin
2022-12-28 12:33 ` Miaohe Lin
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=Y62NVThhnGtnj71u@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linmiaohe@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®