From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [GIT PULL] [ARM] Please pull from git://denx.de/git/u-boot-arm.git
Date: Tue, 14 Aug 2007 18:09:38 +0200 [thread overview]
Message-ID: <20070814160938.F2AC3246FC@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 14 Aug 2007 16:08:11 BST." <000001c7de84$ee21a460$821ba8c0@Emea.Arm.com>
Dear Peter,
in message <000001c7de84$ee21a460$821ba8c0@Emea.Arm.com> you wrote:
>
> Please pull from git://denx.de/git/u-boot-arm.git
>
> It (actually) contains the following changes from Ulf - next time the commit
> messages
> will match the CHANGELOG entries......
>
> Add MACH_TYPE records for several AT91 boards
> Merge to two at45.c files into a common file and split to at45.c and spi.c
> Fix spelling error in DM9161 PHY Support
> Initialize at91rm9200 board (and set LED)
> Add PIO control for at91rm9200dk LEDs and Mux.
> Change dataflash partition boundaries to be compatible with Linux 2.6
>
> Signed-off-by: Peter Pearse <peter.pearse@arm.com>
> Signed-off-by: Ulf Samuelsson <ulf@atmel.com>
>
> Unfortunately I shall not have time to request any more pulls before 17th
> August 2007.
thanks, done.
Here a few comments regarding the code changes:
There were coding style issues in the following files:
* Trailing white space: board/at91rm9200dk/mux.c, drivers/at45.c,
drivers/dataflash.c, include/at45.h, include/dataflash.h
* Trailing empty lines: board/at91rm9200dk/mux.c, cpu/arm920t/at91rm9200/spi.c,
drivers/at45.c, include/led.h
I cleaned this up already.
The following issues need to be addressed:
include/led.h => seems specific to the at91rm9200dk board only,
please move to board directory. Also, the calls to
these functions should be handled without #ifdef's
in common code. Either use existing functions hooks,
or weak references.
drivers/at45.c => has coding style issues - indentation of long,
wrapped around lines is broken.
cpu/arm920t/start.S => I'm surprised to see a lot of intialization
code has now been added to the "reset" entry point.
Is this by accident, or am I missing something?
include/config_cmd_all.h: "CONFIG_CMD_MUX" is a pretty generic name,
while here it is used for a board or CPU specific
feature only. I suggest you rename this into
something which has a "AT91" in the name, like
"CONFIG_CMD_AT91_SPIMUX" or so.
Thanks again.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Q: How do you spell "onomatopoeia"?
A: The way it sounds.
next prev parent reply other threads:[~2007-08-14 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 15:08 [U-Boot-Users] [GIT PULL] [ARM] Please pull from git://denx.de/git/u-boot-arm.git Peter Pearse
2007-08-14 16:09 ` Wolfgang Denk [this message]
2007-08-14 16:45 ` Peter Pearse
2007-08-14 18:39 ` Wolfgang Denk
2007-08-15 11:40 ` [U-Boot-Users] [GIT PULL] [ARM] Please pull fromgit://denx.de/git/u-boot-arm.git Ulf Samuelsson
2007-08-16 9:40 ` Wolfgang Denk
2007-08-28 16:14 ` Peter Pearse
2007-08-28 22:59 ` [U-Boot-Users] ARM cleanup - was: " Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2007-09-11 15:31 [U-Boot-Users] [GIT PULL] [ARM] Please pull from git://denx.de/git/u-boot-arm.git Peter Pearse
2007-09-15 19:22 ` Wolfgang Denk
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=20070814160938.F2AC3246FC@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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