From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH V2 5/6] include: Add declaration of struct msqid64_ds
Date: Tue, 16 Jun 2020 18:11:50 +0200 [thread overview]
Message-ID: <20200616161150.GA20634@dell5510> (raw)
In-Reply-To: <7616a6fa4f1502dde4417d33aa88836c8020419e.1592302358.git.viresh.kumar@linaro.org>
Hi Viresh,
> +++ b/configure.ac
> @@ -153,6 +153,7 @@ AC_CHECK_TYPES([struct iovec],,,[#include <sys/uio.h>])
> AC_CHECK_TYPES([struct ipc64_perm],,,[#include <sys/ipcbuf.h>])
> AC_CHECK_TYPES([struct semid64_ds],,,[#include <sys/sem.h>])
> AC_CHECK_TYPES([struct shmid64_ds],,,[#include <sys/shmbuf.h>])
> +AC_CHECK_TYPES([struct msqid64_ds],,,[#include <sys/msgbuf.h>])
NOTE (for next time): we try to keep items in configure.ac alphabetically sorted :).
Kind regards,
Petr
next prev parent reply other threads:[~2020-06-16 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 10:20 [LTP] [PATCH V2 0/6] syscalls: Add tests to verify the _time_high fields Viresh Kumar
2020-06-16 10:20 ` [LTP] [PATCH V2 1/6] include: Add declaration of struct semid64_ds Viresh Kumar
2020-06-16 10:20 ` [LTP] [PATCH V2 2/6] syscalls: semctl: Add new test to verify the _time_high fields Viresh Kumar
2020-06-16 10:20 ` [LTP] [PATCH V2 3/6] include: Add declaration of struct shmid64_ds Viresh Kumar
2020-06-16 10:20 ` [LTP] [PATCH V2 4/6] syscalls: shmctl: Add new test to verify the _time_high fields Viresh Kumar
2020-06-16 10:20 ` [LTP] [PATCH V2 5/6] include: Add declaration of struct msqid64_ds Viresh Kumar
2020-06-16 16:11 ` Petr Vorel [this message]
2020-06-17 4:30 ` Viresh Kumar
2020-06-16 10:20 ` [LTP] [PATCH V2 6/6] syscalls: msgctl: Add new test to verify the _time_high fields Viresh Kumar
2020-06-16 13:10 ` [LTP] [PATCH V2 0/6] syscalls: Add tests " Cyril Hrubis
2020-06-16 14:29 ` Cyril Hrubis
2020-06-17 4:49 ` 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=20200616161150.GA20634@dell5510 \
--to=pvorel@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