From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH 4/5] x86/vgtod: Remove unused typedef gtod_long_t
Date: Mon, 1 Jul 2024 16:19:20 +0100 [thread overview]
Message-ID: <4d4efa29-8a6e-40de-8979-3fd13d6bd4db@arm.com> (raw)
In-Reply-To: <20240701-vdso-cleanup-v1-4-36eb64e7ece2@linutronix.de>
On 01/07/2024 15:47, Anna-Maria Behnsen wrote:
> The typedef gtod_long_t is not used anymore so remove it.
>
> The header file contains then only includes dependent on
> CONFIG_GENERIC_GETTIMEOFDAY to not break ARCH=um. Nevertheless, keep the
> header file only with those includes to prevent spreading ifdeffery all
> over the place.
>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: x86@kernel.org
> Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> ---
> arch/x86/include/asm/vgtod.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/x86/include/asm/vgtod.h b/arch/x86/include/asm/vgtod.h
> index 7aa38b2ad8a9..a0ce291abcae 100644
> --- a/arch/x86/include/asm/vgtod.h
> +++ b/arch/x86/include/asm/vgtod.h
> @@ -14,11 +14,6 @@
>
> #include <uapi/linux/time.h>
>
> -#ifdef BUILD_VDSO32_64
> -typedef u64 gtod_long_t;
> -#else
> -typedef unsigned long gtod_long_t;
> -#endif
> #endif /* CONFIG_GENERIC_GETTIMEOFDAY */
>
> #endif /* _ASM_X86_VGTOD_H */
>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2024-07-01 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 14:47 [PATCH 0/5] vdso (generic and x86): Misc minor cleanups Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 1/5] vdso/gettimeofday: Clarify comment about open coded function Anna-Maria Behnsen
2024-07-01 14:58 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 2/5] vdso: Add comment about reason for vdso struct ordering Anna-Maria Behnsen
2024-07-01 15:10 ` Vincenzo Frascino
2024-07-01 15:31 ` Anna-Maria Behnsen
2024-07-01 16:17 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 3/5] x86/vdso: Fix function reference in comment Anna-Maria Behnsen
2024-07-01 15:11 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 4/5] x86/vgtod: Remove unused typedef gtod_long_t Anna-Maria Behnsen
2024-07-01 15:19 ` Vincenzo Frascino [this message]
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 5/5] x86/vdso: Remove unused include Anna-Maria Behnsen
2024-07-01 16:19 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
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=4d4efa29-8a6e-40de-8979-3fd13d6bd4db@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=anna-maria@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--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