From: "Kani, Toshi" <toshi.kani@hpe.com>
To: Justin He <Justin.He@arm.com>, Borislav Petkov <bp@alien8.de>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: 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
Date: Tue, 9 Aug 2022 14:57:25 +0000 [thread overview]
Message-ID: <PH7PR84MB1838B57BCEBEF1D8E02CD12D82629@PH7PR84MB1838.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DBBPR08MB4538A3F6A2F63B3AC8223FA6F7629@DBBPR08MB4538.eurprd08.prod.outlook.com>
On Tuesday, August 9, 2022 4:06 AM, Justin He wrote:
> > ghes_edac_init() is called from the normal module init path, e.g.,
> > module_init().
> Thanks for the suggestion, one gap is that under module_init path, how can
> we pass the 2nd parameter of ghes_edac_register (struct device *dev) to
> the new * ghes_edac_init()?
>
> IIUC, the parameter of any functions under module_init() path should be
> void.
Since simpler version of ghes_edac_register() is still called with
the parameters first, it can save *dev to a ghes_edac structure for
ghes_edac_init() to use.
Toshi
prev parent reply other threads:[~2022-08-09 15:22 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
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 [this message]
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=PH7PR84MB1838B57BCEBEF1D8E02CD12D82629@PH7PR84MB1838.NAMPRD84.PROD.OUTLOOK.COM \
--to=toshi.kani@hpe.com \
--cc=James.Morse@arm.com \
--cc=Justin.He@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=rafael@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.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®