linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mathieu Malaterre <malat@debian.org>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: add missing prototype for ‘arch_post_acpi_subsys_init’
Date: Thu, 17 May 2018 12:15:04 +0200	[thread overview]
Message-ID: <1741093.hO3EZQahsV@aspire.rjw.lan> (raw)
In-Reply-To: <20180505203603.4071-1-malat@debian.org>

On Saturday, May 5, 2018 10:36:03 PM CEST Mathieu Malaterre wrote:
> In commit e7ff3a47630d ("x86/amd: Check for the C1E bug post ACPI subsystem
> init") a new function ‘arch_post_acpi_subsys_init’ was introduced. This
> weak function can potentially be overridden on a per arch basis, introduce
> the prototype for clarity.
> 
> Silence the following gcc warning (W=1):
> 
>   init/main.c:484:20: warning: no previous prototype for ‘arch_post_acpi_subsys_init’ [-Wmissing-prototypes]
> 
> Signed-off-by: Mathieu Malaterre <malat@debian.org>
> ---
>  include/linux/acpi.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index 15bfb15c2fa5..cb4d7b6b085c 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -578,6 +578,7 @@ int acpi_match_platform_list(const struct acpi_platform_list *plat);
>  
>  extern void acpi_early_init(void);
>  extern void acpi_subsystem_init(void);
> +extern void arch_post_acpi_subsys_init(void);
>  
>  extern int acpi_nvs_register(__u64 start, __u64 size);
>  
> 

Applied, thanks!

      reply	other threads:[~2018-05-17 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 20:36 [PATCH] acpi: add missing prototype for ‘arch_post_acpi_subsys_init’ Mathieu Malaterre
2018-05-17 10:15 ` Rafael J. Wysocki [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=1741093.hO3EZQahsV@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malat@debian.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;
as well as URLs for NNTP newsgroup(s).