From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-arch@vger.kernel.org, linux-arch-owner@vger.kernel.org,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
torvalds@linux-foundation.org
Subject: Re: [PATCH 0/14] score - New architecure port to SunplusCT S+CORE
Date: Tue, 9 Jun 2009 18:37:28 +0200 [thread overview]
Message-ID: <200906091837.28897.arnd@arndb.de> (raw)
In-Reply-To: <OF47CBE0C5.C2291ED8-ON482575CF.00287989-482575CF.0028F312@sunplusct.com>
On Monday 08 June 2009, liqin.chen@sunplusct.com wrote:
> Thanks Arnd, our MIS help me solve the download problem.
>
> > Feel free to base you code on top of asm-generic.git#next, but tell me
> > when you intend to do that so I can warn you of possibly rebases.
>
> Last week, I had updated score code base on asm-generic.git#next.
>
> and I will apply a account on kernel.org, But before I get the account,
> can you let score code merge in asm-generic.git?
I can take your patches and apply them to a new branch in my tree
if that helps. I hope that Linus can pull my tree early in the
merge window so your architecture port and the microblaze changes
based on it can also get in soon.
I guess for the new architecture, it makes sense to combine all
your patches into a single changeset in git, since they don't
make sense until you have the complete set, and your changeset
comments are rather boring so far anyway.
Can you write a few paragraphs of text about your architecture
for the initial changeset comment? I think it would be good
to permanently store some facts in there, e.g. in which ways
the architecture is different from others, where to get a
toolchain and what kinds of hardware exist for it.
I'll go through the patches once more and see if I find anything
that should still be changed before the code goes in, but
from a brief look, the code looks pretty good now.
Arnd <><
next prev parent reply other threads:[~2009-06-09 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFBE107210.5CC63061-ON482575C7.00354DAD-482575C7.00372848@sunplusct.com>
2009-05-31 14:00 ` [PATCH 0/14] score - New architecure port to SunplusCT S+CORE Arnd Bergmann
2009-06-08 7:23 ` liqin.chen
2009-06-09 16:37 ` Arnd Bergmann [this message]
2009-06-10 2:14 ` liqin.chen
2009-06-10 2:14 ` liqin.chen
2009-04-08 7:18 liqin.chen
2009-04-10 6:06 ` Andrew Morton
2009-05-14 8:44 ` Arnd Bergmann
2009-05-31 9:59 ` liqin.chen
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=200906091837.28897.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kyle@mcmartin.ca \
--cc=linux-arch-owner@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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 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.