From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Russell King <linux@armlinux.org.uk>,
Dave Martin <dave.martin@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: sparse warnings for arch/arm64/kernel/vdso/vgettimeofday.c
Date: Thu, 28 Nov 2019 10:44:03 +0000 [thread overview]
Message-ID: <848ca352-ea77-9840-d94a-96cc78b79795@arm.com> (raw)
In-Reply-To: <bc4cc5c0-5192-4772-5444-17bba3ab74fa@free.fr>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Hello Marc,
On 26/11/2019 10:42, Marc Gonzalez wrote:
> Hello,
>
> Running 'make C=2' on v5.4 (arm64 defconfig) outputs:
>
> CHECK arch/arm64/kernel/vdso/vgettimeofday.c
[...]
>
>
> Are the above warnings all false positives?
> Do I need to update my version of sparse maybe?
>
I downloaded the latest git of sparse and seems that the only warning I am
getting is:
linux/lib/vdso/gettimeofday.c:224:5: warning: symbol '__cvdso_clock_getres' was
not declared. Should it be static?
which seems legitimate. I am going to post a fix to it.
> Regards.
>
--
Regards,
Vincenzo
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 14291 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-28 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 10:42 sparse warnings for arch/arm64/kernel/vdso/vgettimeofday.c Marc Gonzalez
2019-11-28 10:44 ` Vincenzo Frascino [this message]
2019-11-28 12:24 ` Marc Gonzalez
2019-11-28 12:29 ` Vincenzo Frascino
2020-01-23 9:58 ` Marc Gonzalez
2020-01-23 10:10 ` Vincenzo Frascino
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=848ca352-ea77-9840-d94a-96cc78b79795@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=marc.w.gonzalez@free.fr \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).