From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
torvalds@linux-foundation.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 0/14] score - New architecure port to SunplusCT S+CORE
Date: Sun, 31 May 2009 14:00:58 +0000 [thread overview]
Message-ID: <200905311400.58509.arnd@arndb.de> (raw)
In-Reply-To: <OFBE107210.5CC63061-ON482575C7.00354DAD-482575C7.00372848@sunplusct.com>
On Sunday 31 May 2009 09:58:28 liqin.chen@sunplusct.com wrote:
> Hi Arnd,
>
> > Have you had a chance to look at the asm-generic header files I posted
> > a few times?
> >
> > ...
> > Please tell me if you find problems in the generic header files during
> > the conversion.
> >
>
> I can't clone the linux/kernel/git/arnd/asm-generic.git repository,
> and have not test score arch code until now.
Hmm, what is the error message you get? It works fine here:
arnd@wuerfel:/tmp$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
Initialized empty Git repository in /tmp/asm-generic/.git/
remote: Counting objects: 1180676, done.
remote: Compressing objects: 100% (189568/189568), done.
remote: Total 1180676 (delta 984963), reused 1179831 (delta 984290)
Receiving objects: 100% (1180676/1180676), 288.80 MiB | 1308 KiB/s, done.
Resolving deltas: 100% (984963/984963), done.
Checking out files: 100% (27918/27918), done.
arnd@wuerfel:/tmp$ cd asm-generic/
arnd@wuerfel:/tmp/asm-generic$ git checkout -b next origin/next
Branch next set up to track remote branch refs/remotes/origin/next.
Switched to a new branch "next"
> In addition, next time I send the patches mail should base on
> linux/kernel/git/arnd/asm-generic.git or
> linux/kernel/git/sfr/linux-next.git?
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.
The easiest way for you to merge code would be if you can arrange to have
a git account on kernel.org (see http://www.kernel.org/faq/#account), on
your company web server, or on a free hosting service like github.com
or gitorious.org.
Your patches or git tree should merge fine with the linux-next tree so
that Stephen can pick them up as early as possibly, but in general they
should not be _based_ on linux-next because that would mean that
Linus needs to pull all of linux-next in order to merge your code.
Arnd <><
next parent reply other threads:[~2009-05-31 14:02 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 ` Arnd Bergmann [this message]
2009-06-08 7:23 ` [PATCH 0/14] score - New architecure port to SunplusCT S+CORE liqin.chen
2009-06-09 16:37 ` Arnd Bergmann
2009-06-10 2:14 ` liqin.chen
2009-04-08 7:18 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=200905311400.58509.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kyle@mcmartin.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox