public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Liqin Chen <liqin299@gmail.com>
Cc: Lennox Wu <lennox.wu@gmail.com>,
	linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiang Liu <jiang.liu@huawei.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Remove support for score architecture
Date: Tue, 03 Sep 2013 21:19:19 -0700	[thread overview]
Message-ID: <5226B4C7.9050509@roeck-us.net> (raw)
In-Reply-To: <CAFP0e=Gio_o6QFboVGe3aBCM0zFrsrJuNBthj63RXr+=SDPp7Q@mail.gmail.com>

On 09/02/2013 09:54 PM, Liqin Chen wrote:
>
> 2013/9/3 Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>>
>
>     On 09/02/2013 08:18 AM, Lennox Wu wrote:
>
>         Before we start the development of the S+core, Sunplus had licensed
>         ARM and MIPS. We develop S+core for other reason such as the price.
>         Some products on the web of Sunplus adopt S+core , for example
>         the SPV7050.(http://w3.sunplus.__com/products/spv7050.asp <http://w3.sunplus.com/products/spv7050.asp>) These products
>         could still be bought from the market. Some high-end products adopt
>         ARM or MIPS. So, there is no conflict for a company adopts multiple
>         architectures.
>
>         As I said, we recognize that we rarely update because of the limited
>         applications and rare requests from customers. Maybe we don’t
>         understand the culture enough; we think that it is unnecessary if we
>         have no new bugs or new functions, the thought seems wrong. We can
>         commit some patches in the near future.
>
>
>     The point is not about submitting patches, it is about maintaining the code.
>     Even if you don't add functionality, one would expect that you ensure that
>     new kernel versions compile and run on your hardware.
>
>     Since January 2012, 68 patches have been applied to arch/score, pretty
>     much all of them addressing kernel API changes or global cleanup.
>     Only two of them got an Ack by one of the score maintainers.
>     This strongly suggests that you don't keep track of what is going on,
>     and at the very least raises the question if you do compile and test
>     new kernel versions on a regular basis. Even if you do, no one knows
>     about it, because ....
>
>     As part of this process, I would expect the architecture maintainer to
>     accept incoming patches, test the same, and send pull requests to Linus.
>     The last time this happened was early 2011; since then all score patches
>     were sent to Linus through Andrew and a few other maintainers.
>     Actually, I don't see many signoffs from a score maintainer at all,
>     even from the very beginning.
>
>     As pointed out, the MAINTAINERS entry for score points to a
>     non-existing domain, as does the e-mail address of one of the
>     maintainers.
>
>     I would not call that "maintained".
>
>
>
> Hi Al Viro, Guenter Roeck, Arnd Bergmann and all,
>
> I still supports the S+core team to maintain their codes, although I
> left sunplus co. in 2011.
>
> I keep reading the mailing list and testing these patches for S+core,
> I think the main problems are they have not echoed to any comments on
> score's questions. Maybe they think the current situation is good
> enough for their customers, and they don’t understand the rules of the
> group enough. Even so, they should update score code to the latest
> status, include my mail address.
>
> We will discuss how to maintain the code of S+core. However, if all of
> you and Linus also think the S+core should be removed from the
> upstream, we will do it.
>

Trying to build gcc for score says:

*** Configuration score-unknown-elf is obsolete.
*** Specify --enable-obsolete to build it anyway.
*** Support will be REMOVED in the next major release of GCC,
*** unless a maintainer comes forward.

That does not sound very encouraging.

Guenter


  parent reply	other threads:[~2013-09-04  4:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31  2:00 [PATCH] Remove support for score architecture Guenter Roeck
2013-08-31 18:55 ` Arnd Bergmann
2013-08-31 19:40   ` Al Viro
2013-09-02  4:13 ` Lennox Wu
2013-09-02  5:39   ` Guenter Roeck
2013-09-02 15:18     ` Lennox Wu
2013-09-02 15:57       ` Al Viro
2013-09-02 17:29       ` Guenter Roeck
     [not found]         ` <CAFP0e=Gio_o6QFboVGe3aBCM0zFrsrJuNBthj63RXr+=SDPp7Q@mail.gmail.com>
2013-09-03 15:26           ` Guenter Roeck
2013-09-04  4:19           ` Guenter Roeck [this message]
2013-09-05 13:41 ` Rob Landley
2013-09-05 16:13   ` Guenter Roeck

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=5226B4C7.9050509@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiang.liu@huawei.com \
    --cc=lennox.wu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin299@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --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