Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
Cc: 'James Bottomley' <James.Bottomley@HansenPartnership.com>,
	linux-arch@vger.kernel.org
Subject: RE: [PATCHv1 000/211] unicore32 architecture support
Date: Mon, 13 Dec 2010 10:51:20 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1012131049350.2653@localhost6.localdomain6> (raw)
In-Reply-To: <004c01cb9a93$1e17b010$5a471030$@mprc.pku.edu.cn>

On Mon, 13 Dec 2010, Guan Xuetao wrote:

> > > > > These patches add support for UniCore-32 ISA in linux kernel.
> > > > > UniCore ISA is defined and developed by Micro-Processor R&D Center of
> > > > > Peking University, and over the years, the CPUs and SoCs using UniCore ISA
> > > > > have been successfully applied in a variety of products in China.
> > > >
> > > > Could we at least have these 212 emails threaded at least below this
> > > > email ... for those of us who may be tempted to skip a full review with
> > > > a thread delete?
> > 
> > Please don't drop cc's ... someone else may be wondering the same thing
> > so keeping the archive preserves the searchable knowledge.
> Ok, I see.
> 
> > > What's meaning for '212 email threaded below this email'?
> > 
> > Your subject [PATCHv1 000/211] means there are 211 patches plus a
> > description in the set ... that means 212 emails.  If you thread them
> > all below the 000/211 email, it's far easier to handle.
> The rule in Documentations/SubmittingPatches:
>   Do not send more than 15 patches at once to the vger mailing lists!
> So, I suppose I could post 15 patches every two or three days.

As Arnd and myself said before, having less but larger patches which
group the files into topics is a far better solution than sending 200+
patches which touch single files.

Thanks,

	tglx

      reply	other threads:[~2010-12-13  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  9:28 [PATCHv1 000/211] unicore32 architecture support Guan Xuetao
2010-12-09  9:50 ` Tejun Heo
2010-12-09 13:49   ` Thomas Gleixner
2010-12-09 14:05     ` Tejun Heo
2010-12-09 14:18       ` Thomas Gleixner
2010-12-09 14:27         ` Tejun Heo
2010-12-10  8:56     ` Guan Xuetao
2010-12-10 11:01       ` Thomas Gleixner
2010-12-10 12:35         ` Arnd Bergmann
2010-12-10 12:16     ` Arnd Bergmann
2010-12-09 17:50 ` James Bottomley
     [not found]   ` <028701cb9919$df3b7900$9db26b00$@mprc.pku.edu.cn>
     [not found]     ` <1292078266.4722.2.camel@mulgrave.site>
2010-12-13  6:58       ` Guan Xuetao
2010-12-13  9:51         ` 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.1012131049350.2653@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=guanxuetao@mprc.pku.edu.cn \
    --cc=linux-arch@vger.kernel.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