From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Miaohe Lin <linmiaohe@huawei.com>, rafael@kernel.org
Cc: lenb@kernel.org, james.morse@arm.com, tony.luck@intel.com,
bp@alien8.de, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: APEI: mark some functions __init
Date: Tue, 20 Jun 2023 11:43:29 +0800 [thread overview]
Message-ID: <638b32ce-d2a8-2686-dda1-26abb0778bae@linux.alibaba.com> (raw)
In-Reply-To: <20230617080708.2002287-1-linmiaohe@huawei.com>
On 2023/6/17 16:07, Miaohe Lin wrote:
> hest_esrc_len() and apei_hest_parse() are only called inside __init
> section. So mark them __init too.
Hi, Miaohe,
should ghes_estatus_pool_init also be marked with __init?
Thanks.
Best Regards,
Shuai
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> drivers/acpi/apei/hest.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c
> index 6aef1ee5e1bd..2d78e808ab8b 100644
> --- a/drivers/acpi/apei/hest.c
> +++ b/drivers/acpi/apei/hest.c
> @@ -55,7 +55,7 @@ static inline bool is_generic_error(struct acpi_hest_header *hest_hdr)
> hest_hdr->type == ACPI_HEST_TYPE_GENERIC_ERROR_V2;
> }
>
> -static int hest_esrc_len(struct acpi_hest_header *hest_hdr)
> +static int __init hest_esrc_len(struct acpi_hest_header *hest_hdr)
> {
> u16 hest_type = hest_hdr->type;
> int len;
> @@ -88,7 +88,7 @@ static int hest_esrc_len(struct acpi_hest_header *hest_hdr)
>
> typedef int (*apei_hest_func_t)(struct acpi_hest_header *hest_hdr, void *data);
>
> -static int apei_hest_parse(apei_hest_func_t func, void *data)
> +static int __init apei_hest_parse(apei_hest_func_t func, void *data)
> {
> struct acpi_hest_header *hest_hdr;
> int i, rc, len;
next prev parent reply other threads:[~2023-06-20 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 8:07 [PATCH] ACPI: APEI: mark some functions __init Miaohe Lin
2023-06-20 3:43 ` Shuai Xue [this message]
2023-06-20 3:58 ` 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=638b32ce-d2a8-2686-dda1-26abb0778bae@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.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