From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] ARM:OMAP3:SDP3430: initial support
Date: Sat, 19 Sep 2009 10:43:01 -0500 [thread overview]
Message-ID: <4AB4FC05.8060505@gmail.com> (raw)
In-Reply-To: <1253370896.27060.28.camel@ptyser-laptop>
Peter Tyser said the following on 09/19/2009 09:34 AM:
thanks for your review
> Hi Nishanth,
>
> On Fri, 2009-09-18 at 21:21 -0500, Nishanth Menon wrote:
>
>> From: David Brownell <david-b@pacbell.net>
>>
>> Start of SDP3430 support in "mainline"
>> u-boot mainline code
>>
>> Original Patch written by David Brownell
>>
>
> I don't think the above comments are necessary. David will be credited
> with authorship already, and the subject line and text below make it
> clear what this patch does.
>
>
Ack..
>> create mode 100644 board/ti/sdp3430/sdp.h
>> create mode 100644 board/ti/sdp3430/u-boot.lds
>> create mode 100644 include/configs/omap3_sdp.h
>>
>
> The board config header file should be renamed to sdp.h from
> omap3_sdp.h. There was a recent thread discussing this convention "ARM
> Pull Request" around Sept 6.
>
sdp3430 - there are many software development platforms ->
omap2420 based, omap2430 based etc..
Thanks for pointing this chain out.. a specific link describing
the thought will help and prevent me misunderstanding the
intention here.
>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e9db278..adc8a63 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -619,6 +619,7 @@ Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>> Nishanth Menon <nm@ti.com>
>>
>> omap3_zoom1 ARM CORTEX-A8 (OMAP3xx SoC)
>> + omap3_sdp ARM CORTEX-A8 (OMAP3xx SoC)
>>
>
> You may as well keep the boards ordered alphabetically (and remove the
> omap_ prefix from sdp).
>
ack to alphabetical sort.
>> +/******************************************************************************
>> + * Routine: board_init
>> + * Description: Early hardware init.
>> + *****************************************************************************/
>> +int board_init(void)
>> +{
>> + DECLARE_GLOBAL_DATA_PTR;
>> +
>>
>
>
> I'd use the preferred multi-line comment style:
> /*
> *
> */
>
> There are lots of other non-preferred multi-line comments throughout the
> patch as well.
>
ack.
> I personally don't think its necessary to put "Routine: <name>" stuff
> for each function either. It doesn't add any benefit, adds cruft to
> grep output, and might get out of sync with the real function name at
> some point. If it were me, I would get rid of "Description: " text too.
> Its pretty obvious that the text "Early hardware init" is a description
> of the function.
>
not to all.. I dont like it either, I would rather go doxygen style..
will convert.
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-09-19 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 2:21 [U-Boot] [PATCH 0/6] ARM:OMAP3:SDP3430 initial support Nishanth Menon
2009-09-19 2:21 ` [U-Boot] [PATCH 1/6] OMAP3: Fix SDRC init Nishanth Menon
2009-09-19 2:21 ` [U-Boot] [PATCH 2/6] OMAP3: export enable_gpmc_cs_config to board files Nishanth Menon
2009-09-19 2:21 ` [U-Boot] [PATCH 3/6] OMAP3: make gpmc_config as const Nishanth Menon
2009-09-19 2:21 ` [U-Boot] [PATCH 4/6] OMAP3: fix warnings when NAND/ONENAND is not used Nishanth Menon
2009-09-19 2:21 ` [U-Boot] [PATCH 5/6] DLMALLOC:!X86: add av_ initialization Nishanth Menon
2009-09-19 2:21 ` [U-Boot] [PATCH 6/6] ARM:OMAP3:SDP3430: initial support Nishanth Menon
2009-09-19 14:34 ` Peter Tyser
2009-09-19 15:43 ` Nishanth Menon [this message]
2009-09-20 1:27 ` Paulraj, Sandeep
2009-09-23 19:51 ` Wolfgang Denk
2009-09-24 0:47 ` Nishanth Menon
2009-09-19 14:03 ` [U-Boot] [PATCH 5/6] DLMALLOC:!X86: add av_ initialization Peter Tyser
2009-09-19 15:37 ` Nishanth Menon
2009-09-19 17:30 ` Peter Tyser
2009-09-23 20:04 ` Wolfgang Denk
2009-09-24 0:50 ` Nishanth Menon
2009-09-23 19:55 ` [U-Boot] [PATCH 1/6] OMAP3: Fix SDRC init 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=4AB4FC05.8060505@gmail.com \
--to=menon.nishanth@gmail.com \
--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