public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 00/27] score arch files for linux
@ 2009-06-09  6:20 liqin.chen
  2009-06-09 17:00 ` Arnd Bergmann
  2009-06-09 18:19 ` Arnd Bergmann
  0 siblings, 2 replies; 4+ messages in thread
From: liqin.chen @ 2009-06-09  6:20 UTC (permalink / raw)
  To: linux-arch, linux-kernel; +Cc: Arnd Bergmann, Andrew Morton, torvalds

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.

Best Regards
Liqin

--

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH 00/27] score arch files for linux
  2009-06-09  6:20 [PATCH 00/27] score arch files for linux liqin.chen
@ 2009-06-09 17:00 ` Arnd Bergmann
  2009-06-09 18:19 ` Arnd Bergmann
  1 sibling, 0 replies; 4+ messages in thread
From: Arnd Bergmann @ 2009-06-09 17:00 UTC (permalink / raw)
  To: liqin.chen; +Cc: linux-arch, linux-kernel, Andrew Morton, torvalds

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 <><

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH 00/27] score arch files for linux
  2009-06-09  6:20 [PATCH 00/27] score arch files for linux liqin.chen
  2009-06-09 17:00 ` Arnd Bergmann
@ 2009-06-09 18:19 ` Arnd Bergmann
  2009-06-13  6:50   ` liqin.chen
  1 sibling, 1 reply; 4+ messages in thread
From: Arnd Bergmann @ 2009-06-09 18:19 UTC (permalink / raw)
  To: liqin.chen; +Cc: linux-arch, linux-kernel, Andrew Morton, torvalds

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.

Ok, just finished looking over the patches and I am generally
very happy about their quality, it usually takes much longer
for a submission of this size to get into a mergeable shape.

The only thing that I think needs to be fixed before a
2.6.31 release is my comment about unistd.h still containing
the __ARCH_WANT_SYSCALL_* #defines. I consider that my fault
because I did not make it clear enough what those are meant
for in asm-generic/unistd.h.

One more general thought: I noticed that you split the header
files by alphabetical ordering. While there is no good way to
split a set of interdependent files, a logical grouping
(e.g. ABI, memory management, device, cpu) would be nice.

Everything else I found are only polite suggestions of what
can still be improved, not issues that I think need to
be addressed immediately. I especially love how the work
that Remis and I put into the generic header files starts
paying off, because it makes reviewing an architecture so
much simpler.

Please add my 'Reviewed-by: Arnd Bergmann <arnd@arndb.de>'
to your patches.

Thanks,

	Arnd <><

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH 00/27] score arch files for linux
  2009-06-09 18:19 ` Arnd Bergmann
@ 2009-06-13  6:50   ` liqin.chen
  0 siblings, 0 replies; 4+ messages in thread
From: liqin.chen @ 2009-06-13  6:50 UTC (permalink / raw)
  To: Arnd Bergmann; +Cc: Andrew Morton, linux-arch, linux-kernel, torvalds

Hi Arnd,

Arnd Bergmann <arnd@arndb.de> 写于 2009-06-10 02:19:06:

> 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.
> 
> Ok, just finished looking over the patches and I am generally
> very happy about their quality, it usually takes much longer
> for a submission of this size to get into a mergeable shape.
> 
> The only thing that I think needs to be fixed before a
> 2.6.31 release is my comment about unistd.h still containing
> the __ARCH_WANT_SYSCALL_* #defines. I consider that my fault
> because I did not make it clear enough what those are meant
> for in asm-generic/unistd.h.
> 
> One more general thought: I noticed that you split the header
> files by alphabetical ordering. While there is no good way to
> split a set of interdependent files, a logical grouping
> (e.g. ABI, memory management, device, cpu) would be nice.
> 
> Everything else I found are only polite suggestions of what
> can still be improved, not issues that I think need to
> be addressed immediately. I especially love how the work
> that Remis and I put into the generic header files starts
> paying off, because it makes reviewing an architecture so
> much simpler.
> 
> Please add my 'Reviewed-by: Arnd Bergmann <arnd@arndb.de>'
> to your patches.
> 

Based on your comments, I use asm-generic/current.h, hardirq.h,
unaligned.h etc instead of files under arch/include/asm folder.
It could work in score code.

Best Regards
Liqin
--



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-06-13  6:55 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-09  6:20 [PATCH 00/27] score arch files for linux liqin.chen
2009-06-09 17:00 ` Arnd Bergmann
2009-06-09 18:19 ` Arnd Bergmann
2009-06-13  6:50   ` liqin.chen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox