From: Arnaud Patard <apatard@mandriva.com>
To: yanhua <yanh@lemote.com>
Cc: linux-mips@linux-mips.org, "Ralf Baechle" <ralf@linux-mips.org>,
彭亮锦 <penglj@lemote.com>,
"zhangfx@lemote.com" <zhangfx@lemote.com>
Subject: Re: [PATCH 1/14] lemote: Loongson2F based machines support
Date: Thu, 09 Apr 2009 10:39:26 +0200 [thread overview]
Message-ID: <m3prfm6x1d.fsf@anduin.mandriva.com> (raw)
In-Reply-To: <49DD7E88.7040305@lemote.com> (yanhua's message of "Thu, 09 Apr 2009 12:50:16 +0800")
yanhua <yanh@lemote.com> writes:
Hi,
> Mini fuloong, yeeloong are all Loongson2F based systems. Loongson2F have
> builtin DDR2 and PCIX controller. The PCIX controller have a similar
> programming interface with FPGA northbridge used in Loongson2E.
First, please read Documentation/SubmittingPatches first. There's no
signed-off-by and this patch is too big. So big patches are making
review a nightmare, please split it into smaller pieces :(
Also, I'd like to see a different directories layout. You're doing :
arch/mips/lemote/
lm2e/
lm2f/
common/
fuloong/
yeeloong/
This is quite annoying because:
- I'll prefer seeing loongson instead of Lemote. I've some ST machines
here they do share a lot of code with the 2e/2f so I'd like to avoid
duplicating code.
- There's some code very similar between 2e, 2f-yeelong and
2f-fuloong and other machines. Why not putting them in a common
directory instead of duplicating again some code ?
To sum up, imho, it would be better to have something like :
arch/mips/loongson/
common/
2e/
2f/ (or something similar)
common/
yeelong/
fuloong/
...
Arnaud
next prev parent reply other threads:[~2009-04-09 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 4:50 [PATCH 1/14] lemote: Loongson2F based machines support yanhua
2009-04-09 8:39 ` Arnaud Patard [this message]
2009-04-09 9:01 ` yanhua
2009-04-13 11:36 ` Zhang Le
2009-04-13 12:25 ` yanhua
2009-04-09 14:16 ` Philippe Vachon
2009-04-09 14:43 ` yanhua
2009-04-14 9:46 ` Zhang Le
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=m3prfm6x1d.fsf@anduin.mandriva.com \
--to=apatard@mandriva.com \
--cc=linux-mips@linux-mips.org \
--cc=penglj@lemote.com \
--cc=ralf@linux-mips.org \
--cc=yanh@lemote.com \
--cc=zhangfx@lemote.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