From: Jan Kiszka <jan.kiszka@siemens.com>
To: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] [PULL] Fixes for forge
Date: Fri, 17 Jul 2015 14:57:45 +0200 [thread overview]
Message-ID: <55A8FBC9.3080207@siemens.com> (raw)
The following changes since commit 81958c620029485f3533b72f42b31ffb05eae234:
cobalt/thread, copperplate: fetch per-thread user window from the global heap (2015-07-16 21:24:33 +0200)
are available in the git repository at:
git://git.xenomai.org/xenomai-jki.git for-forge
for you to fetch changes up to 9e297aa3edcf73454524106346420061d10d1208:
cobalt/kernel: Generate cobalt_syscalls and cobalt_sysmodes (2015-07-16 23:48:50 +0200)
I've left out the mayday topic for now as it has known issues on
non-x86 / depends on I-pipe changes there.
----------------------------------------------------------------
Jan Kiszka (6):
cobalt/kernel: Fix mode of mayday syscall
cobalt/posix/sem: Do not register named semaphores with process resources
cobalt/kernel: Mark backtrace syscall as lostage
cobalt/kernel: Fix locking for xnthread info manipulations
cobalt/kernel: Set commas in syscall tables inside the macros
cobalt/kernel: Generate cobalt_syscalls and cobalt_sysmodes
.../arch/x86/include/asm/xenomai/syscall32.h | 12 +-
kernel/cobalt/posix/Makefile | 12 ++
kernel/cobalt/posix/gen-syscall-entries.sh | 32 +++
kernel/cobalt/posix/sem.c | 19 +-
kernel/cobalt/posix/syscall.c | 218 ++-------------------
kernel/cobalt/synch.c | 2 +
kernel/cobalt/thread.c | 3 +
scripts/prepare-kernel.sh | 4 +-
8 files changed, 85 insertions(+), 217 deletions(-)
create mode 100755 kernel/cobalt/posix/gen-syscall-entries.sh
reply other threads:[~2015-07-17 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55A8FBC9.3080207@siemens.com \
--to=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.