From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: caiyinyu <caiyinyu@loongson.cn>,
libc-alpha@sourceware.org, i.swmail@xen0n.name
Cc: joseph_myers@mentor.com, carlos@redhat.com, xuchenghua@loongson.cn
Subject: Re: [PATCH 2/3] LoongArch: Fix VDSO_HASH and VDSO_NAME.
Date: Thu, 28 Jul 2022 09:57:19 -0300 [thread overview]
Message-ID: <e5bfd835-a9c9-8b9a-7321-9998c5afe78b@linaro.org> (raw)
In-Reply-To: <20220728073009.2588790-3-caiyinyu@loongson.cn>
On 28/07/22 04:30, caiyinyu wrote:
> ---
> sysdeps/unix/sysv/linux/loongarch/sysdep.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sysdeps/unix/sysv/linux/loongarch/sysdep.h b/sysdeps/unix/sysv/linux/loongarch/sysdep.h
> index 306e0af3a3..8a398adb70 100644
> --- a/sysdeps/unix/sysv/linux/loongarch/sysdep.h
> +++ b/sysdeps/unix/sysv/linux/loongarch/sysdep.h
> @@ -110,8 +110,8 @@
>
> #ifndef __ASSEMBLER__
>
> -#define VDSO_NAME "LINUX_2.6"
> -#define VDSO_HASH 61765110
> +#define VDSO_NAME "LINUX_5.10"
> +#define VDSO_HASH 182947696
>
> /* List of system calls which are supported as vsyscalls. */
> #define HAVE_CLOCK_GETRES64_VSYSCALL "__vdso_clock_getres"
LGTM and it is ok for 2.36, thanks.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
next prev parent reply other threads:[~2022-07-28 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 7:30 [PATCH 0/3] GLIBC LOONGARCH PATCHES caiyinyu
2022-07-28 7:30 ` [PATCH 1/3] LoongArch: Add vdso support for gettimeofday caiyinyu
2022-07-28 12:58 ` Adhemerval Zanella Netto
2022-07-29 15:10 ` Carlos O'Donell
2022-08-03 3:12 ` caiyinyu
2022-07-28 7:30 ` [PATCH 2/3] LoongArch: Fix VDSO_HASH and VDSO_NAME caiyinyu
2022-07-28 12:57 ` Adhemerval Zanella Netto [this message]
2022-07-28 7:30 ` [PATCH 3/3] LoongArch: Add greg_t and gregset_t caiyinyu
2022-07-28 12:57 ` Adhemerval Zanella Netto
2022-07-28 12:53 ` [PATCH 0/3] GLIBC LOONGARCH PATCHES Adhemerval Zanella Netto
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=e5bfd835-a9c9-8b9a-7321-9998c5afe78b@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=carlos@redhat.com \
--cc=i.swmail@xen0n.name \
--cc=joseph_myers@mentor.com \
--cc=libc-alpha@sourceware.org \
--cc=xuchenghua@loongson.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).