From: Thomas Gleixner <tglx@linutronix.de>
To: liqin.chen@sunplusct.com
Cc: Will Newton <will.newton@gmail.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH 0/13] score - New architecure port to SunplusCT S+CORE processor
Date: Fri, 27 Mar 2009 11:29:26 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0903271125380.3397@localhost.localdomain> (raw)
In-Reply-To: <OF39905543.8F85F55B-ON48257586.000793DC-48257586.0007F946@sunplusct.com>
On Fri, 27 Mar 2009, liqin.chen@sunplusct.com wrote:
> > >> > We would like to release a patch for kernel 2.6.29-rc8.
> > >> > This patch include score header files, arch files and serial driver
> > > for
> > >> > spct6600(score core) platform.
> > >> >
> > >> > For the other driver patches, I'll send them one by one in
> > >> > small size latter. Thanks!
> > >> >
> > >> > Would you merge them to the stock kernel?
> > >> >
> > >> > Patch information is slightly bigger, so I placed it on our
> SunplusCT
> > > web
> > >> > site.
> > >> >
> > >
> http://www.sunplusct.com/images/linux-score-patch/linux-score-20090324.patch
Please split the patches further into logical and reviewable
pieces. Also each patch needs a patch description which will be the
change log in the git repository and your Signed-off-by line. Also
each patch needs a unique and useful subject line in the mail.
Download references for such patches are useless.
See Documentation/SubmittingPatches
Thanks,
tglx
prev parent reply other threads:[~2009-03-27 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 4:11 [PATCH] " liqin.chen
2009-03-25 12:01 ` Will Newton
2009-03-27 1:25 ` [PATCH 0/13] " liqin.chen
2009-03-27 10:29 ` Thomas Gleixner [this message]
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=alpine.LFD.2.00.0903271125380.3397@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=torvalds@linux-foundation.org \
--cc=will.newton@gmail.com \
/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
all inboxes | Powered by JetHome®