From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Mayday mechanism broken on x86-64 - simpler approach feasible?
Date: Mon, 16 Feb 2015 18:37:47 +0100 [thread overview]
Message-ID: <54E22AEB.1010508@siemens.com> (raw)
In-Reply-To: <54DCE6D6.7060305@siemens.com>
On 2015-02-12 18:45, Jan Kiszka wrote:
>>> Ok. While we are at it, we should get rid of the syscall return type in
>>> the COBALT_SYSCALL[_DECL] macro helpers, this is pointless.
>>
>> Jep, that's what I did - hard-wired it to long.
>>
>> First tests look good, just need to split things up into 3 or 4 patches now.
>
> Done, see my for-forge branch.
BTW, we should also clean up the 32-bit syscall macros in the same way,
just to be consistent (on issue to fix over there). Can do when I ran
out of bugs (or need some distraction).
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-02-16 17:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 16:57 [Xenomai] Mayday mechanism broken on x86-64 - simpler approach feasible? Jan Kiszka
2014-12-17 17:19 ` Philippe Gerum
2014-12-17 17:17 ` Gilles Chanteperdrix
2014-12-17 17:36 ` Jan Kiszka
2014-12-17 17:45 ` Gilles Chanteperdrix
2014-12-17 17:49 ` Jan Kiszka
2014-12-17 17:37 ` Jan Kiszka
2014-12-17 17:52 ` Philippe Gerum
2014-12-17 17:46 ` Jan Kiszka
2014-12-17 18:28 ` Philippe Gerum
2014-12-17 18:32 ` Jan Kiszka
2014-12-17 18:33 ` Jan Kiszka
2014-12-17 18:55 ` Philippe Gerum
2014-12-17 18:57 ` Jan Kiszka
2015-02-03 15:29 ` Philippe Gerum
2015-02-12 16:36 ` Jan Kiszka
2015-02-12 17:01 ` Philippe Gerum
2015-02-12 17:02 ` Jan Kiszka
2015-02-12 17:07 ` Philippe Gerum
2015-02-12 17:16 ` Jan Kiszka
2015-02-12 17:18 ` Philippe Gerum
2015-02-12 17:19 ` Jan Kiszka
2015-02-12 17:45 ` Jan Kiszka
2015-02-16 17:37 ` Jan Kiszka [this message]
2015-02-16 17:43 ` Philippe Gerum
2015-02-17 10:58 ` Philippe Gerum
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=54E22AEB.1010508@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=rpm@xenomai.org \
--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.