From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>,
"chensong_2000@189.cn" <chensong_2000@189.cn>
Cc: "chensong@tj.kylinos.cn" <chensong@tj.kylinos.cn>
Subject: Re: [PATCH v5 1/5] y2038: cobalt/posix/clock: Adding clock_gettime64
Date: Fri, 23 Apr 2021 14:46:01 +0000 [thread overview]
Message-ID: <e1a882afd7369a6e0ff592f34e953b9b2b74860a.camel@siemens.com> (raw)
In-Reply-To: <1618993992-21069-1-git-send-email-chensong_2000@189.cn>
On Wed, 2021-04-21 at 16:33 +0800, Song Chen wrote:
> From: chensong <chensong@tj.kylinos.cn>
>
> Add a syscall specific for clock_gettime with 64bit
> time_t.
>
> Signed-off-by: chensong <chensong@tj.kylinos.cn>
>
>
> diff --git a/include/cobalt/uapi/syscall.h b/include/cobalt/uapi/syscall.h
> index 8895d2b..9859963 100644
> --- a/include/cobalt/uapi/syscall.h
> +++ b/include/cobalt/uapi/syscall.h
> @@ -123,6 +123,7 @@
> #define sc_cobalt_clock_adjtime 100
> #define sc_cobalt_thread_setschedprio 101
> #define sc_cobalt_sem_timedwait64 102
> +#define sc_cobalt_clock_gettime64 103
>
My fault didn't notice that during review but now while preparing the
wiki stuff for being available inside the Xenomai hacker space:
The next syscall would be clock_getres64 instead of clock_gettime64
next prev parent reply other threads:[~2021-04-23 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 8:33 [PATCH v5 1/5] y2038: cobalt/posix/clock: Adding clock_gettime64 Song Chen
2021-04-23 11:10 ` Bezdeka, Florian
2021-04-23 11:48 ` chensong
2021-04-23 14:46 ` Bezdeka, Florian [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-20 6:22 Song Chen
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=e1a882afd7369a6e0ff592f34e953b9b2b74860a.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=chensong@tj.kylinos.cn \
--cc=chensong_2000@189.cn \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.