From: Ley Foon Tan <lftan@altera.com>
To: linux-kernel@vger.kernel.org, arnd@arndb.de
Cc: linux-arch@vger.kernel.org
Subject: Generic syscall ABI support
Date: Thu, 28 Mar 2013 11:09:42 +0800 [thread overview]
Message-ID: <1364440182.2289.45.camel@leyfoon-vm> (raw)
Need advise regarding the generic syscall ABI support.
We are planning to upstream our Nios II kernel (arch/nios2) to mainline.
But it doesn't support generic syscall ABI yet (It requires an updated
Glibc port as well).
The question is, is it a requirement for new arch to support generic
syscall ABI when upstreaming? Can we upstream a non-generic syscall ABI
first and migrate to generic syscall ABI in future?
Thanks.
Regards
LFTAN
WARNING: multiple messages have this Message-ID (diff)
From: Ley Foon Tan <lftan@altera.com>
To: <linux-kernel@vger.kernel.org>, <arnd@arndb.de>
Cc: <linux-arch@vger.kernel.org>
Subject: Generic syscall ABI support
Date: Thu, 28 Mar 2013 11:09:42 +0800 [thread overview]
Message-ID: <1364440182.2289.45.camel@leyfoon-vm> (raw)
Need advise regarding the generic syscall ABI support.
We are planning to upstream our Nios II kernel (arch/nios2) to mainline.
But it doesn't support generic syscall ABI yet (It requires an updated
Glibc port as well).
The question is, is it a requirement for new arch to support generic
syscall ABI when upstreaming? Can we upstream a non-generic syscall ABI
first and migrate to generic syscall ABI in future?
Thanks.
Regards
LFTAN
next reply other threads:[~2013-03-28 3:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 3:09 Ley Foon Tan [this message]
2013-03-28 3:09 ` Generic syscall ABI support Ley Foon Tan
2013-03-28 5:35 ` H. Peter Anvin
2013-03-28 7:44 ` Arnd Bergmann
2013-03-28 8:32 ` Ley Foon Tan
2013-03-28 8:32 ` Ley Foon Tan
2013-03-28 10:40 ` Arnd Bergmann
2013-03-28 11:30 ` Ley Foon Tan
2013-03-28 11:30 ` Ley Foon Tan
2013-03-28 11:42 ` Arnd Bergmann
2013-03-29 4:41 ` Rob Landley
2013-03-29 4:53 ` H. Peter Anvin
2013-03-29 9:49 ` Ley Foon Tan
2013-03-29 9:49 ` Ley Foon Tan
2013-03-29 10:42 ` Arnd Bergmann
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=1364440182.2289.45.camel@leyfoon-vm \
--to=lftan@altera.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.