From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/5] syscalls: semctl: Add new test to verify the _time_high fields
Date: Thu, 21 May 2020 16:26:21 +0200 [thread overview]
Message-ID: <20200521142621.GE7833@yuki.lan> (raw)
In-Reply-To: <CAK8P3a0pxv5wauMcf223n=_7zNJ4mn1Y0WvcssFC13pcvz9wmQ@mail.gmail.com>
Hi!
> > The _time_high fields must be reset by the kernel, add a test to verify
> > that.
> >
> > Suggested-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Right, here you do need to copy the struct definitions since I forgot
> to add a way to detect the presence in the kernel header files,
> sorry about that.
>
> Possibly you could just have a check in the Makefile that lets
> skips the test if it fails to build because of old kernel headers?
> Or maybe check LINUX_VERSION_CODE to see if the headers
> are at least from linux-4.19?
We usually include autotools checks and fallback definitions in
include/lapi.h in this case.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-05-21 14:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 10:47 [LTP] [PATCH 0/5] syscalls: Add tests to verify the _time_high fields Viresh Kumar
2020-05-21 10:47 ` [LTP] [PATCH 1/5] syscalls:ipc: Move libraries to libs/ director Viresh Kumar
2020-05-22 12:39 ` Cyril Hrubis
2020-05-26 3:08 ` Viresh Kumar
2020-05-29 5:39 ` Yang Xu
2020-06-15 12:20 ` Cyril Hrubis
2020-05-21 10:47 ` [LTP] [PATCH 2/5] include: Add declaration of struct ipc64_perm Viresh Kumar
2020-05-21 13:11 ` Arnd Bergmann
2020-05-22 7:10 ` Viresh Kumar
2020-05-22 7:16 ` [LTP] [PATCH V2 " Viresh Kumar
2020-06-15 12:43 ` Cyril Hrubis
2020-06-16 6:41 ` Viresh Kumar
2020-06-16 9:53 ` Cyril Hrubis
2020-06-16 18:56 ` [LTP] [PATCH " Petr Vorel
2020-05-21 10:47 ` [LTP] [PATCH 3/5] syscalls: semctl: Add new test to verify the _time_high fields Viresh Kumar
2020-05-21 13:20 ` Arnd Bergmann
2020-05-21 14:26 ` Cyril Hrubis [this message]
2020-05-22 7:12 ` Viresh Kumar
2020-05-22 7:16 ` [LTP] [PATCH V2 " Viresh Kumar
2020-06-15 13:31 ` Cyril Hrubis
2020-06-16 6:40 ` Viresh Kumar
2020-06-16 9:52 ` Cyril Hrubis
2020-06-16 10:09 ` Viresh Kumar
2020-06-16 12:41 ` Cyril Hrubis
2020-05-21 10:47 ` [LTP] [PATCH 4/5] syscalls: shmctl: " Viresh Kumar
2020-06-15 13:33 ` Cyril Hrubis
2020-05-21 10:47 ` [LTP] [PATCH 5/5] syscalls: msgctl: " Viresh Kumar
2020-06-15 13:38 ` Cyril Hrubis
2020-05-21 13:08 ` [LTP] [PATCH 0/5] syscalls: Add tests " Arnd Bergmann
2020-05-21 14:25 ` Cyril Hrubis
2020-05-21 14:29 ` Cyril Hrubis
2020-05-22 9:08 ` Viresh Kumar
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=20200521142621.GE7833@yuki.lan \
--to=chrubis@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox