From: Alejandro Colomar <alx.manpages@gmail.com>
To: enh <enh@google.com>, linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] vdso.7: fix risc-v symbol names.
Date: Tue, 31 Jan 2023 13:51:59 +0100 [thread overview]
Message-ID: <b1496bcd-4cf5-ba8c-8e83-c262f4af178e@gmail.com> (raw)
In-Reply-To: <CAJgzZoqTHGh-VLMSN7H6t9K95TddyCRm2L6f-mnYv6dSquc3nQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1325 bytes --]
Hi!
On 1/31/23 00:02, enh wrote:
> The kernel git history says the names have always been "__vdso_" rather
> than "__kernel_", so I assume this was a copy & paste mistake from a
> different architecture.
>
> Luckily, the path to the kernel source that lets you confirm/deny this
> _is_ correct :-)
Could you please sign the patch?
Also, it seems something is broken in the patch; maybe the mailer broke it? I
can't seem to apply it. Please check.
Cheers,
Alex
> ---
> man7/vdso.7 | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/man7/vdso.7 b/man7/vdso.7
> index fabb34d0d..9f47efc7d 100644
> --- a/man7/vdso.7
> +++ b/man7/vdso.7
> @@ -459,12 +459,12 @@ The table below lists the symbols exported by the vDSO.
> l l.
> symbol version
> _
> -__kernel_rt_sigreturn LINUX_4.15
> -__kernel_gettimeofday LINUX_4.15
> -__kernel_clock_gettime LINUX_4.15
> -__kernel_clock_getres LINUX_4.15
> -__kernel_getcpu LINUX_4.15
> -__kernel_flush_icache LINUX_4.15
> +__vdso_rt_sigreturn LINUX_4.15
> +__vdso_gettimeofday LINUX_4.15
> +__vdso_clock_gettime LINUX_4.15
> +__vdso_clock_getres LINUX_4.15
> +__vdso_getcpu LINUX_4.15
> +__vdso_flush_icache LINUX_4.15
> .TE
> .if t \{\
> .in
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-31 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 23:02 [PATCH] vdso.7: fix risc-v symbol names enh
2023-01-31 12:51 ` Alejandro Colomar [this message]
2023-01-31 17:39 ` enh
2023-01-31 23:59 ` Alejandro Colomar
2023-02-01 19:39 ` enh
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=b1496bcd-4cf5-ba8c-8e83-c262f4af178e@gmail.com \
--to=alx.manpages@gmail.com \
--cc=enh@google.com \
--cc=linux-man@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox