mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Yao Zi <ziyao@disroot.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [RFC PATCH] time.h: drop non-standard and out-of-date CLOCK_SGI_CYCLE
Date: Fri, 21 Feb 2025 19:27:25 -0500	[thread overview]
Message-ID: <20250222002725.GF1827@brightrain.aerifal.cx> (raw)
In-Reply-To: <20241121174015.1518-2-ziyao@disroot.org>

On Thu, Nov 21, 2024 at 05:40:16PM +0000, Yao Zi wrote:
> This definition was introduced in commit d74e462a ("add CLOCK_TAI (and
> CLOCK_SGI_CYCLE) clock ids to time.h added in linux-v3.10 commit
> 1ff3c9677bff7e468e0c487d0ffefe4e901d33f4"). However, it's actually a
> platform specific feature, available only on SGI SN2 IA64 systems. Its
> Linux support has been removed later in commit 07903ada9613
> ("mmtimer: Remove the SGI SN2 mmtimer driver").
> 
> Having this definition is known to cause applications misdetect the
> environment. There's no reason to keep a non-standard, seldom-available
> and removed-since-4.13-kernel macro in a standard header.
> 
> Signed-off-by: Yao Zi <ziyao@disroot.org>
> ---
>  include/time.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/include/time.h b/include/time.h
> index 3d948372..0fe02111 100644
> --- a/include/time.h
> +++ b/include/time.h
> @@ -94,7 +94,6 @@ struct itimerspec {
>  #define CLOCK_BOOTTIME           7
>  #define CLOCK_REALTIME_ALARM     8
>  #define CLOCK_BOOTTIME_ALARM     9
> -#define CLOCK_SGI_CYCLE         10
>  #define CLOCK_TAI               11
>  
>  #define TIMER_ABSTIME 1
> -- 
> 2.47.0

I think this looks ok. Any objections?

Rich

  reply	other threads:[~2025-02-22  0:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 17:40 Yao Zi
2025-02-22  0:27 ` Rich Felker [this message]
2025-02-22  3:17   ` Yao Zi

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=20250222002725.GF1827@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=ziyao@disroot.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).