All of lore.kernel.org
 help / color / mirror / Atom feed
From: Song Chen <chensong_2000@189.cn>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: jan.kiszka@siemens.com, xenomai@xenomai.org
Subject: Re: y2038: Migrate from syscall() to XENOMAI_SYSCALLx()
Date: Sat, 8 May 2021 09:40:46 +0800	[thread overview]
Message-ID: <6095EC1E.7000601@189.cn> (raw)
In-Reply-To: <20210507140559.1099146-1-florian.bezdeka@siemens.com>

noticed, i will submit a patch to address it specifically.

Song


On 2021年05月07日 22:05, Florian Bezdeka wrote:
> Hi Song,
>                                                                           
> you may have already noticed that we had a problem running the y2038 on
> some ARM boards. The problem was detected once Jan picked the series of
> the sem_timedwait64 implementation into next and triggered a test run on
> real hardware.
>                                                                           
> As a result I had to migrate from syscall() to XENOMAI_SYSCALLx().
>                                                                           
> As the acutal change is hard to find in v4 that I recently pushed to the
> list: Here is "patch" that shows the pattern I used.
>                                                                           
> Sadly replacing the function call is not enough because glibc
> "communicates" using "errno", while the Xenomai interface does not.
>                                                                           
> How to deal with your patches? Any chance that you could "migrate"
> as well? Or should I try to find some time to do that?
>
> Best regards,
> Florian
>



      reply	other threads:[~2021-05-08  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 14:05 y2038: Migrate from syscall() to XENOMAI_SYSCALLx() Florian Bezdeka
2021-05-08  1:40 ` Song Chen [this message]

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=6095EC1E.7000601@189.cn \
    --to=chensong_2000@189.cn \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --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.