Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
Cc: 'Tejun Heo' <tj@kernel.org>, '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 12:01:51 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1012101156230.2653@localhost6.localdomain6> (raw)
In-Reply-To: <026901cb9848$17e71ac0$47b55040$@mprc.pku.edu.cn>

On Fri, 10 Dec 2010, Guan Xuetao wrote:
> 
> > -----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

Please fix your mail client to do proper citations. A single line 

On Thu, 9 Dec 2010, Thomas Gleixner wrote:

or whatever your preferred cite line is, is sufficient. We all have
the mail header already.
 
> > 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.

And please mail them to yourself before you post them and make sure
they apply and resemble exaclty what you wanted to send. I just
noticed, that your mailer line-wrapped the patches:

+       /*
+        * actually the registers should be pushed and pop'd conditionally,
but
+        * after bl the flags are certainly clobbered
+        */

Thanks,

	tglx

  reply	other threads:[~2010-12-10 11:02 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 [this message]
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

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.1012101156230.2653@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=guanxuetao@mprc.pku.edu.cn \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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