From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>
Cc: ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] nanosleep: use POSIX runtime detection for CLOCK_MONOTONIC
Date: Thu, 16 Apr 2026 12:04:21 +0000 [thread overview]
Message-ID: <69e0d046.5d0a0220.852a3.35df@mx.google.com> (raw)
In-Reply-To: <20260416115801.GA299728@pevik>
Hi Petr,
> I'd hope agent would find other '#ifdef _POSIX_MONOTONIC_CLOCK' use without
> <unistd.h> which is in
> testcases/open_posix_testsuite/conformance/interfaces/clock_settime/helpers.h
It's one rule behind to make agent discovering this. There's no rule
in the actually c-tests.md agent configuration about this particular
case. I personally never add any include to the file if it's imported
already from other headers.
But we know that everyone has their own opiinon when it comes to C :-)
Should we add a rule to the agent spotting/ignoring these corner cases?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-16 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 6:59 [LTP] [PATCH] nanosleep: use POSIX runtime detection for CLOCK_MONOTONIC Andrea Cervesato
2026-04-16 8:03 ` [LTP] " linuxtestproject.agent
2026-04-16 11:58 ` Petr Vorel
2026-04-16 12:04 ` Andrea Cervesato via ltp [this message]
2026-04-16 12:08 ` [LTP] [PATCH] " Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2026-04-16 12:33 [LTP] [PATCH v2] " Andrea Cervesato
2026-04-16 13:45 ` [LTP] " linuxtestproject.agent
2026-05-04 13:20 [LTP] [PATCH] " Andrea Cervesato
2026-05-04 14:05 ` [LTP] " linuxtestproject.agent
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=69e0d046.5d0a0220.852a3.35df@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@gmail.com \
--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 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.