From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: opendmb@gmail.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nathan Lynch <nathan_lynch@mentor.com>,
open list <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Alexios Zavras <alexios.zavras@intel.com>,
bcm-kernel-feedback-list@broadcom.com,
Russell King <rmk+kernel@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Enrico Weigelt <info@metux.net>
Subject: Re: [PATCH] ARM: VDSO: Match ARMv8 timer in cntvct_functional()
Date: Tue, 28 Jan 2020 11:26:20 -0800 [thread overview]
Message-ID: <9efff584-5e2f-df15-3eea-9cf4f31f8f27@gmail.com> (raw)
In-Reply-To: <20200116235731.22395-1-f.fainelli@gmail.com>
On 1/16/2020 3:57 PM, Florian Fainelli wrote:
> It is possible for a system with an ARMv8 timer to run a 32-bit kernel.
> When this happens we will unconditionally have the vDSO code remove the
> __vdso_gettimeofday and __vdso_clock_gettime symbols because
> cntvct_functional() returns false since it does not match that
> compatibility string.
>
> Fixes: ecf99a439105 ("ARM: 8331/1: VDSO initialization, mapping, and synchronization")
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Submitted:
https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=8957/1
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-28 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 23:57 [PATCH] ARM: VDSO: Match ARMv8 timer in cntvct_functional() Florian Fainelli
2020-01-28 19:26 ` Florian Fainelli [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=9efff584-5e2f-df15-3eea-9cf4f31f8f27@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alexios.zavras@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan_lynch@mentor.com \
--cc=opendmb@gmail.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@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).