From: "Simon Zeni" <[email protected]>
To: "Jens Axboe" <[email protected]>, <[email protected]>
Subject: Re: [PATCH] examples: disable ucontext-cp if ucontext.h is not available
Date: Wed, 28 Oct 2020 20:53:26 -0400 [thread overview]
Message-ID: <C6OYQ7AU7G3Z.2XB9LZ8CPC23V@gengar> (raw)
In-Reply-To: <[email protected]>
On Wed Oct 28, 2020 at 12:33 PM EDT, Jens Axboe wrote:
> It's been a while since I double checked 5.4-stable, I bet a lot of
> these
> are due to the tests not being very diligent in checking what is and
> what
> isn't supported. I'll take a look and rectify some of that.
I tried with 5.9.1 and fewer tests failed.
```
Tests failed: <defer> <double-poll-crash> <file-register>
<io_uring_enter> <io_uring_register> <iopoll> <poll-cancel-ton>
<read-write> <rename> <sq-poll-dup> <sq-poll-share> <unlink>
```
It might be due to musl, I'll as I use the library and send the
necessary patches if needed.
Simon
next prev parent reply other threads:[~2020-10-29 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 2:31 [PATCH] examples: disable ucontext-cp if ucontext.h is not available Simon Zeni
2020-10-28 22:33 ` Jens Axboe
2020-10-29 0:53 ` Simon Zeni [this message]
2020-10-29 1:06 ` Jens Axboe
2020-10-29 1:23 ` Simon Zeni
2020-10-29 3:00 ` Jens Axboe
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=C6OYQ7AU7G3Z.2XB9LZ8CPC23V@gengar \
[email protected] \
[email protected] \
[email protected] \
/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