All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org
Subject: Re: [PATCH 00/27] score arch files for linux
Date: Tue, 9 Jun 2009 19:00:31 +0200	[thread overview]
Message-ID: <200906091900.32379.arnd@arndb.de> (raw)
In-Reply-To: <OF54D30DF0.6974DE98-ON482575D0.0021670B-482575D0.00234606@sunplusct.com>

On Tuesday 09 June 2009, liqin.chen@sunplusct.com wrote:
> Hi Arnd, Andrew Morton and linus,
> 
> According to your comment on score arch code, 
> we update score code base on asm-generic#next repository.
> use arch microblaze and blackfin as reference.
>

Some general notes about the patch submission, not the contents:
Your mail client still has a 'wordwrap' problem, which breaks
importing the patches into a repository. The easiest workaround
for this is to use 'git send-email', which handles it correctly.
Play around with the '--dry-run' and '--suppress-cc=all' options
at first to send the patches to yourself, so you know how it
works.

For 'git format-patch', please use the '-M -B --thread=shallow'
options so that all your mails end up nicely in a single mail
thread and renames are detected (the latter would not change
anything for your current set of patches, but may some day).

	Arnd <><

  reply	other threads:[~2009-06-09 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  6:20 [PATCH 00/27] score arch files for linux liqin.chen
2009-06-09 17:00 ` Arnd Bergmann [this message]
2009-06-09 18:19 ` Arnd Bergmann
2009-06-13  6:50   ` liqin.chen
2009-06-13  6:50     ` 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=200906091900.32379.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --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 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.