public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] openposix: update invalid clock id to accomodate new auxiliary clock ids
Date: Mon, 6 Oct 2025 11:56:45 +0200	[thread overview]
Message-ID: <aOOSXW1LpFRqtHBS@yuki.lan> (raw)
In-Reply-To: <20251006094344.GB66983@pevik>

Hi!
> Thanks for info. Out of curiosity: I suppose the different approach from the
> exact value for LTP Linux tests fixed in 5c0e414511 (which use lib/tst_clocks.c)
> is because POSIX tests can be tested for other Unix like tests? Is the POSIX
> testsuite intended for BSD or any unix like kernels/OS? If yes, I wonder if
> anybody does (and if it even compiles).

If I remmeber correctly we got some feedback from Haiku OS devs and BSD
uses LTP as well, even the Linux part to test their Linux compatibility
layer.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-10-06  9:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 10:13 [LTP] [PATCH] openposix: update invalid clock id to accomodate new auxiliary clock ids Avinesh Kumar
2025-10-03 10:25 ` Petr Vorel
2025-10-03 11:30   ` Avinesh Kumar
2025-10-03 12:26     ` Petr Vorel
2025-10-06  8:53 ` Cyril Hrubis
2025-10-06  9:08   ` Cyril Hrubis
2025-10-07 16:03     ` Avinesh Kumar
2025-10-06  9:43   ` Petr Vorel
2025-10-06  9:56     ` Cyril Hrubis [this message]
2025-10-07 14:32   ` [LTP] [PATCH v2] " Avinesh Kumar
2025-10-07 14:36     ` Avinesh Kumar
2025-10-07 21:37       ` Petr Vorel
2025-10-13  9:56         ` Andrea Cervesato via ltp
2025-10-13 11:29           ` Petr Vorel
2025-10-13 14:26             ` Petr Vorel
2025-10-13 14:11     ` Cyril Hrubis

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=aOOSXW1LpFRqtHBS@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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