From: Joerg Vehlow <lkml@jv-coder.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] realtime/m4: Re-add define for robust mutexattr APIs
Date: Thu, 26 Nov 2020 09:30:53 +0100 [thread overview]
Message-ID: <8dc13989-88bf-1727-1dbd-83a2163ffb03@jv-coder.de> (raw)
In-Reply-To: <20201119113816.GH2785@yuki.lan>
Hi,
On 11/19/2020 12:38 PM, Cyril Hrubis wrote:
> 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.
either that or this patch. At least at the moment these tests are
completely broken.
I am not sure how long pthread_mutexattr_*roboust* api is part of posix
and if ltp is supposed to be supported on platforms, that may not
implement it.
But should accepting this patch wouldn't do any harm for now, but would
fix the tests. In the future it can still be removed completely.
J?rg
PS: @Cyril Sorry for the resending this, forgot to include the mail list
next prev parent reply other threads:[~2020-11-26 8:30 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
2020-11-26 8:30 ` Joerg Vehlow [this message]
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=8dc13989-88bf-1727-1dbd-83a2163ffb03@jv-coder.de \
--to=lkml@jv-coder.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox