From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v5] sysdeps/clock_nanosleep: Use clock_nanosleep_time64 if avaliable
Date: Fri, 8 Nov 2019 10:49:50 -0300 [thread overview]
Message-ID: <474360dc-f275-ba83-70fe-7f55181c6096@linaro.org> (raw)
In-Reply-To: <CAKmqyKNM2N2bnZNw2KEo0b1hhFKxCYG_RKEHvP0+-oOA8TLreA@mail.gmail.com>
On 07/11/2019 16:23, Alistair Francis wrote:
> On Thu, Nov 7, 2019 at 11:15 AM Adhemerval Zanella
> <adhemerval.zanella@linaro.org> wrote:
>>
>>
>>
>> On 07/11/2019 15:11, Alistair Francis wrote:
>>> +# endif /* __NR_clock_nanosleep_time64 */
>>> + struct timespec ts32, tr32;
>>> +
>>> + if (! in_time_t_range (req->tv_sec))
>>> + {
>>> + __set_errno (EOVERFLOW);
>>> + return -1;
>>> + }
>>> +
>>> + ts32 = valid_timespec64_to_timespec (*req);
>>> + r = INTERNAL_SYSCALL_CANCEL (clock_nanosleep, err, clock_id, flags,
>>> + &ts32, &tr32);
>>> +
>>> + if ((r == 0 || errno != ENOSYS) && rem)
>>> + *rem = valid_timespec_to_timespec64 (tr32);
>>
>> I think we can assume __NR_nanosleep here.
>
> I'm not sure what you mean
I mean that it does not require to check for ENOSYS.
>
>>
>>> +#endif /* __ASSUME_TIME64_SYSCALLS */
>>> +
>>> return (INTERNAL_SYSCALL_ERROR_P (r, err)
>>> - ? INTERNAL_SYSCALL_ERRNO (r, err) : 0);
>>> + ? INTERNAL_SYSCALL_ERRNO (r, err) : 0);
>>> }
>>
>> This is just replacing a tab with spaces, I don't think it is really required.
>
> It's the only tab in the file. I was cleaning up the indentation while
> touching everything else. I can drop it though.
Afaik glibc code conventions uses tabs for C file indentation (except for some
imported files).
next prev parent reply other threads:[~2019-11-08 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 18:11 [PATCH v5] sysdeps/clock_nanosleep: Use clock_nanosleep_time64 if avaliable Alistair Francis
2019-11-07 19:15 ` Adhemerval Zanella
2019-11-07 19:23 ` Alistair Francis
2019-11-07 19:37 ` Alistair Francis
2019-11-08 13:49 ` Adhemerval Zanella [this message]
2019-11-08 17:08 ` Alistair Francis
2019-11-08 12:54 ` Lukasz Majewski
2019-11-08 16:56 ` Alistair Francis
2019-11-08 17:07 ` Alistair Francis
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=474360dc-f275-ba83-70fe-7f55181c6096@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=alistair23@gmail.com \
--cc=libc-alpha@sourceware.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).