public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: S+core architecture (arch/score/) support files
Date: Tue, 23 Jun 2009 11:43:22 +0200	[thread overview]
Message-ID: <200906231143.22985.arnd@arndb.de> (raw)
In-Reply-To: <OF318304AE.9C3DA8BC-ON482575DE.002B7553-482575DE.002FC96B@sunplusct.com>

On Tuesday 23 June 2009, liqin.chen@sunplusct.com wrote:
> Hi Linus,
> 
> This repository contains Linux support for S+core CPU.
> 
> Please pull
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git score

I've helped Liquin getting this into a state for inclusion,
so I'll share my observations about the submission.

The code looks very clean for a new architecture support, with the
exception of a few misformatted comments and similar minor issues.
By using the asm-generic headers that are now in 2.6.31, the amount
of copy-paste programming was reduced to a minimum, the total amount
of code added is much less than any other architecture (200kb score,
290kb h8300, 570kb microblaze are the smallest ones).
Fixes for any issues noted during review usually came in quickly.

S+core is now the first architecture to use the ABI defined in
asm-generic, which means it can serve as an example for other
architectures that want to merge their code in the future.

Unfortunately, I don't think that the score glibc has been fully
ported to support this, so it also means that the version that is
being submitted has undergone any run-time testing. I did check
that it compiles fine but could not do more in lack of hardware
or even just a user space distro.

Another small negative is that Liquin is still unexperienced with
the procedures we use in Linux. I've helped out by providing
my git tree, but am not planning to do that beyond 2.6.31.
Given that he has also been upstream gcc maintainer for S+core
for well over 2 years, I believe merging it now will work out well.

	Arnd <><

  reply	other threads:[~2009-06-23  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  8:37 S+core architecture (arch/score/) support files liqin.chen
2009-06-23  9:43 ` Arnd Bergmann [this message]
2009-06-23 10:51   ` liqin.chen
2009-06-23 12:06   ` Andi Kleen
2009-06-23 13:55     ` Arnd Bergmann
2009-06-23 14:30       ` Andi Kleen
2009-06-24  3:22     ` liqin.chen
2009-06-24  7:07       ` Andi Kleen
2009-06-25  3:00         ` liqin.chen
2009-06-23 14:50 ` Christoph Hellwig
2009-07-08 10:53   ` [PATCH] score: add regsets support for score liqin.chen
2009-07-09 15:08     ` Arnd Bergmann
2009-07-09 21:03       ` Roland McGrath
2009-07-10  9:06         ` liqin.chen
2009-07-10  9:43       ` liqin.chen
2009-07-10 10:44         ` 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=200906231143.22985.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin.chen@sunplusct.com \
    --cc=torvalds@linux-foundation.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