From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] realtime/m4: Re-add define for robust mutexattr APIs
Date: Thu, 19 Nov 2020 12:38:16 +0100 [thread overview]
Message-ID: <20201119113816.GH2785@yuki.lan> (raw)
In-Reply-To: <20201119095227.921830-1-lkml@jv-coder.de>
Hi!
The code switched to the POSIX variants later on so I wonder if we even
need this configure check or if we can remove the ifdefs from the
testcases completely.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-11-19 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 9:52 [LTP] [PATCH] realtime/m4: Re-add define for robust mutexattr APIs Joerg Vehlow
2020-11-19 11:38 ` Cyril Hrubis [this message]
2020-11-26 8:30 ` Joerg Vehlow
2020-12-03 12:47 ` 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=20201119113816.GH2785@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