From: Sudeep Holla <sudeep.holla@arm.com>
To: "Ben Dooks (Codethink)" <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH] RFC: cpu-topology: declare parse_acpi_topology in <linux/arch_topology.h>
Date: Mon, 21 Oct 2019 17:52:24 +0100 [thread overview]
Message-ID: <20191021165224.GA8066@bogus> (raw)
In-Reply-To: <20191021162530.13611-1-ben.dooks@codethink.co.uk>
On Mon, Oct 21, 2019 at 05:25:30PM +0100, Ben Dooks (Codethink) wrote:
> The parse_acpi_topology() is not declared anywhere which
> causes the following sparse warning:
>
> drivers/base/arch_topology.c:522:19: warning: symbol 'parse_acpi_topology' was not declared. Should it be static?
>
> RFC: is this the best place to put it?
>
> Signed-off-by: Ben Dooks (Codethink) <ben.dooks@codethink.co.uk>
> ---
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: linux-kernel@vger.kernel.org
> ---
> include/linux/arch_topology.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/arch_topology.h b/include/linux/arch_topology.h
> index 42f2b5126094..7ae32900d9a2 100644
> --- a/include/linux/arch_topology.h
> +++ b/include/linux/arch_topology.h
> @@ -59,4 +59,6 @@ void remove_cpu_topology(unsigned int cpuid);
> void reset_cpu_topology(void);
> #endif
>
> +extern int parse_acpi_topology(void);
> +
Can we drop extern like other declarations here ?
Also move this inside CONFIG_GENERIC_ARCH_TOPOLOGY ?
Please cc Greg with these changes, I will ack and ask Greg to pick up. Thanks.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-10-21 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 16:25 [PATCH] RFC: cpu-topology: declare parse_acpi_topology in <linux/arch_topology.h> Ben Dooks (Codethink)
2019-10-21 16:52 ` Sudeep Holla [this message]
2019-10-22 8:42 ` Ben Dooks
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=20191021165224.GA8066@bogus \
--to=sudeep.holla@arm.com \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.