mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guan Xuetao" <guanxuetao@mprc.pku.edu.cn>
To: "'Thomas Gleixner'" <tglx@linutronix.de>, "'Tejun Heo'" <tj@kernel.org>
Cc: "'Arnd Bergmann'" <arnd@arndb.de>, <linux-arch@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCHv1 000/211] unicore32 architecture support
Date: Fri, 10 Dec 2010 16:56:08 +0800	[thread overview]
Message-ID: <026901cb9848$17e71ac0$47b55040$@mprc.pku.edu.cn> (raw)
In-Reply-To: <alpine.LFD.2.00.1012091443580.2653@localhost6.localdomain6>



> -----Original Message-----
> From: linux-arch-owner@vger.kernel.org [mailto:linux-arch-
> owner@vger.kernel.org] On Behalf Of Thomas Gleixner
> Sent: Thursday, December 09, 2010 9:50 PM
> To: Tejun Heo
> Cc: Guan Xuetao; Arnd Bergmann; linux-arch@vger.kernel.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCHv1 000/211] unicore32 architecture support
> 
> B1;2401;0cOn Thu, 9 Dec 2010, Tejun Heo wrote:
> 
> > Hello,
> >
> > On 12/09/2010 10:28 AM, Guan Xuetao wrote:
> > > From: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
> > >
> > > 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.
> >
> > * Patches should be split according to logical steps of changes, not
> >   per-file.
> >
> > * Patches should be bisectable.  IOW, after applying upto any patch in
> >   the series, the tree should be buildable and working.
> 
> That does not work for a new architecture. There is nothing to bisect.
> 
> > * When posting a patch series, especially one as large as 211, please
> >   make the mails for the actual patches replies to the head message.
> >   Don't post it as 212 separate messages or replies to the immediate
> >   previous patch.
> >
> > So, in short, if you're adding a whole new arch, just post it as a
> > single patch or a series of several patches if it requires changes
> > outside of the specific arch subtree.
> 
> Crap. a single patch is a major PITA for review. It's even worse than
> 211 per file patches.
> 
> It's ok to have several patches ordered by topics
> 
>   - generic header stuff
>   - processor and system headers
>   - low level entry and setup code
>   - process/thread related code
>   - mm related code
>   - timers
>   - interrupts
>   - ptrace
>   - signals
>   - fault handling
>   - misc
>   - build system, main makefile, Kconfig
> 
> That makes it actually feasible to review.
Thanks,
I will rearrange my patches.

Guan Xuetao


  parent reply	other threads:[~2010-12-10  8:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  9:28 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 [this message]
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

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='026901cb9848$17e71ac0$47b55040$@mprc.pku.edu.cn' \
    --to=guanxuetao@mprc.pku.edu.cn \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tj@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

all inboxes | Powered by JetHome®