From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] openposix: update invalid clock id to accomodate new auxiliary clock ids
Date: Fri, 3 Oct 2025 12:25:16 +0200 [thread overview]
Message-ID: <20251003102516.GA27492@pevik> (raw)
In-Reply-To: <20251003101310.13359-1-akumar@suse.de>
Hi Avinesh,
> There can be 8 more clock ids reserved on systems with
> CONFIG_POSIX_AUX_CLOCK=y [1]
> consequently clock 17 no longer remains an invalid id.
Thanks for fixing this! Because we don't have infrastructure to check kconfig in
open POSIX tests I agree to just bump the value.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
> [1] https://lkml.org/lkml/2025/5/19/341
nit: FYI I've noticed several times people suggesting to use for links
lore.kernel.org, see kernel commit 05a5f51ca5666 ("Documentation: Replace
lkml.org links with lore"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05a5f51ca566
Replace the lkml.org links with lore to better use a single source
that's more likely to stay available long-term.
Therefore link would be:
[1] https://lore.kernel.org/lkml/20250519083025.905800695@linutronix.de/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-03 10:25 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 [this message]
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
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=20251003102516.GA27492@pevik \
--to=pvorel@suse.cz \
--cc=akumar@suse.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.