mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin He <Justin.He@arm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Kani, Toshi" <toshi.kani@hpe.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, James Morse <James.Morse@arm.com>,
	Tony Luck <tony.luck@intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Robert Richter <rric@kernel.org>,
	Shuai Xue <xueshuai@linux.alibaba.com>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:EDAC-CORE" <linux-edac@vger.kernel.org>,
	nd <nd@arm.com>
Subject: RE: 回复: [PATCH] ACPI: APEI: move edac_init ahead of ghes platform drv register
Date: Wed, 10 Aug 2022 08:53:14 +0000	[thread overview]
Message-ID: <DBBPR08MB45389F2642CF29EF186E3B22F7659@DBBPR08MB4538.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <YvNsLViKcduXz5px@zn.tnic>



> -----Original Message-----
> From: Borislav Petkov <bp@alien8.de>
> Sent: Wednesday, August 10, 2022 4:28 PM
> To: Justin He <Justin.He@arm.com>
> Cc: Kani, Toshi <toshi.kani@hpe.com>; Rafael J. Wysocki <rafael@kernel.org>;
> Len Brown <lenb@kernel.org>; James Morse <James.Morse@arm.com>;
> Tony Luck <tony.luck@intel.com>; Mauro Carvalho Chehab
> <mchehab@kernel.org>; Robert Richter <rric@kernel.org>; Shuai Xue
> <xueshuai@linux.alibaba.com>; Jarkko Sakkinen <jarkko@kernel.org>; ACPI
> Devel Maling List <linux-acpi@vger.kernel.org>; Linux Kernel Mailing List
> <linux-kernel@vger.kernel.org>; open list:EDAC-CORE
> <linux-edac@vger.kernel.org>
> Subject: Re: 回复: [PATCH] ACPI: APEI: move edac_init ahead of ghes
> platform drv register
> 
> On Wed, Aug 10, 2022 at 06:00:49AM +0000, Justin He wrote:
> > Is this strange or any other side effects?
> 
> This is no different than what we do now on x86 MCA.
> 
> If the logging machinery is modules, they consume error records only when
> loaded.
Ok, got it, thanks a lot
From my local testing, after the provided patch from you + notifier register.
It works after I resolved a few other issues.

When I verify different building kconfig(X86/Arm64, ghes_edac[M]/[*]), and booting, I will send out
the new version.


> 
> Btw, pls get rid of this if you want to be posting on public mailing lists. You can
> ask your other ARM colleagues how they solved it. :)
> 
Sorry, missed one configuration in the mailbox ☹


--
Cheers,
Justin (Jia He)



  reply	other threads:[~2022-08-10  8:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  2:32 Jia He
2022-08-08 18:17 ` Rafael J. Wysocki
2022-08-08 18:37   ` Borislav Petkov
2022-08-08 20:40     ` Kani, Toshi
2022-08-08 20:57       ` Borislav Petkov
2022-08-08 21:11         ` Kani, Toshi
2022-08-08 21:20           ` Borislav Petkov
2022-08-08 21:36             ` Kani, Toshi
2022-08-09  7:40               ` Borislav Petkov
2022-08-09  9:24                 ` 回复: " Justin He
2022-08-09 11:15                   ` Borislav Petkov
2022-08-09 14:36                     ` Kani, Toshi
2022-08-09 15:14                       ` Borislav Petkov
2022-08-09 15:39                         ` Kani, Toshi
2022-08-09 17:11                           ` Borislav Petkov
2022-08-09 17:36                             ` Kani, Toshi
2022-08-09 16:51                     ` Justin He
2022-08-09 17:15                       ` Borislav Petkov
2022-08-09 18:46                         ` Borislav Petkov
2022-08-10  6:00                           ` Justin He
2022-08-10  8:28                             ` Borislav Petkov
2022-08-10  8:53                               ` Justin He [this message]
2022-08-11  0:39                           ` Justin He
2022-08-11  7:40                             ` Borislav Petkov
2022-08-09 10:06       ` Justin He
2022-08-09 14:57         ` Kani, Toshi

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=DBBPR08MB45389F2642CF29EF186E3B22F7659@DBBPR08MB4538.eurprd08.prod.outlook.com \
    --to=justin.he@arm.com \
    --cc=James.Morse@arm.com \
    --cc=bp@alien8.de \
    --cc=jarkko@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nd@arm.com \
    --cc=rafael@kernel.org \
    --cc=rric@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=toshi.kani@hpe.com \
    --cc=xueshuai@linux.alibaba.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®