linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ley Foon Tan <lftan@altera.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Generic syscall ABI support
Date: Thu, 28 Mar 2013 16:32:02 +0800	[thread overview]
Message-ID: <1364459522.2308.6.camel@leyfoon-vm> (raw)
In-Reply-To: <201303280744.27477.arnd@arndb.de>

On Thu, 2013-03-28 at 07:44 +0000, Arnd Bergmann wrote:

> Yes, absolutely. What a couple of the previous architectures have done is
> to keep out of tree patches for their old ABI for a while, and to submit
> only code that follows the generic ABI upstream. Usually it doesn't take
> long for users to migrate to a new user space after that, but it gives
> people a migration strategy. Normally you have other patches that are
> required on top of the stuff that is already upstream while you are
> getting everything merged, so this is not much different to a device
> driver that needs to get rewritten to adapt to a new kernel subsystem.
> 
> 	Arnd
> 
Thanks for the reply. 
We will working on generic ABI for kernel and Glibc. This might take
some times.

Regards
LFTAN

  reply	other threads:[~2013-03-28  8:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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:41               ` Rob Landley
2013-03-29  4:53               ` H. Peter Anvin
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=1364459522.2308.6.camel@leyfoon-vm \
    --to=lftan@altera.com \
    --cc=arnd@arndb.de \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).