From: Alistair Francis <alistair23@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v6 1/3] sysdeps/clock_nanosleep: Use clock_nanosleep_time64 if avaliable
Date: Sun, 10 Nov 2019 08:44:22 -0800 [thread overview]
Message-ID: <CAKmqyKPHDz5ASqGZJ0m8+vnNxXuT0y3ePHkoGbjbSiAgHjJEWw@mail.gmail.com> (raw)
In-Reply-To: <87r22g3y3p.fsf@hase.home>
On Sun, Nov 10, 2019 at 1:00 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> This breaks rt/tst-timer on i586 and powerpc and armv7l.
I don't understand how. I tested it on ARMv7. Do you have any more
details on why it is failing?
Is there a way to run just that test so I don't have to run all the others?
Also is this on a 5.1+ or earlier kernel/headers?
Alistair
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
next prev parent reply other threads:[~2019-11-10 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 17:03 [PATCH v6 1/3] sysdeps/clock_nanosleep: Use clock_nanosleep_time64 if avaliable Alistair Francis
2019-11-08 17:03 ` [PATCH v6 2/3] time: Define time64 thrd_sleep Alistair Francis
2019-11-08 18:58 ` Adhemerval Zanella
2019-11-08 21:17 ` Alistair Francis
2019-11-08 17:03 ` [PATCH v6 3/3] time: Define time64 nanosleep Alistair Francis
2019-11-08 18:59 ` Adhemerval Zanella
2019-11-08 19:01 ` [PATCH v6 1/3] sysdeps/clock_nanosleep: Use clock_nanosleep_time64 if avaliable Adhemerval Zanella
2019-11-08 20:52 ` Alistair Francis
2019-11-10 9:00 ` Andreas Schwab
2019-11-10 16:44 ` Alistair Francis [this message]
2019-11-10 17:44 ` Andreas Schwab
2019-11-11 13:50 ` Adhemerval Zanella
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKmqyKPHDz5ASqGZJ0m8+vnNxXuT0y3ePHkoGbjbSiAgHjJEWw@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).