From: chenlifu <chenlifu@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<feng.tang@intel.com>, <gregkh@linuxfoundation.org>,
<peterz@infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] x86/tsc: Make art_related_clocksource static
Date: Sat, 8 Oct 2022 16:47:35 +0800 [thread overview]
Message-ID: <2a887f96-93d4-90ed-cfc4-61e895b102cf@huawei.com> (raw)
In-Reply-To: <20220823021821.3052159-1-chenlifu@huawei.com>
在 2022/8/23 10:18, Chen Lifu 写道:
> The symbol is not used outside of the file, so mark it static.
>
> Fixes the following warning:
>
> arch/x86/kernel/tsc.c:53:20: warning:
> symbol 'art_related_clocksource' was not declared. Should it be static?
>
> Signed-off-by: Chen Lifu <chenlifu@huawei.com>
> ---
> arch/x86/kernel/tsc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> index cafacb2e58cc..a78e73da4a74 100644
> --- a/arch/x86/kernel/tsc.c
> +++ b/arch/x86/kernel/tsc.c
> @@ -49,11 +49,11 @@ static DEFINE_STATIC_KEY_FALSE(__use_tsc);
> int tsc_clocksource_reliable;
>
> static u32 art_to_tsc_numerator;
> static u32 art_to_tsc_denominator;
> static u64 art_to_tsc_offset;
> -struct clocksource *art_related_clocksource;
> +static struct clocksource *art_related_clocksource;
>
> struct cyc2ns {
> struct cyc2ns_data data[2]; /* 0 + 2*16 = 32 */
> seqcount_latch_t seq; /* 32 + 4 = 36 */
>
friendly ping ...
next prev parent reply other threads:[~2022-10-08 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 2:18 Chen Lifu
2022-10-08 8:47 ` chenlifu [this message]
2022-10-17 14:31 ` [tip: x86/cleanups] " tip-bot2 for Chen Lifu
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=2a887f96-93d4-90ed-cfc4-61e895b102cf@huawei.com \
--to=chenlifu@huawei.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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®