From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv3 0/3] OMAP3: Board specific updates
Date: Mon, 27 Apr 2009 17:39:33 +0200 [thread overview]
Message-ID: <49F5D1B5.8070603@googlemail.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301D73E11A7@dbde02.ent.ti.com>
Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Premi, Sanjeev
>> Sent: Monday, April 27, 2009 8:49 PM
>> To: Dirk Behme
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] [PATCHv3 0/3] OMAP3: Board specific updates
>>
>>
>>> -----Original Message-----
>>> From: Dirk Behme [mailto:dirk.behme at googlemail.com]
>>> Sent: Monday, April 27, 2009 8:47 PM
>>> To: Premi, Sanjeev
>>> Cc: u-boot at lists.denx.de
>>> Subject: Re: [U-Boot] [PATCHv3 0/3] OMAP3: Board specific updates
>>>
>>> Hi Premi,
>>>
>>> Sanjeev Premi wrote:
>>>> This series contains 3 specific updates:
>>>> - Use common API to print cpu and board
>>>> related information.
>>>> - Remove unused board type definitions.
>>>> - Print correct silicon revision in the
>>>> board information
>>>>
>>>> These updates have been tested on OMAP3EVM
>>>> with ES 3.0 and ES3.1 silicon versions.
>>>>
>>>> Thanks to Dirk Behme [dirk.behme at googlemail.com]
>>>> for converting a quick hack into complete
>>>> solution.
>>>>
>>>> Sanjeev Premi (3):
>>>> OMAP3: Use functions print_cpuinfo() and checkboard()
>>>> OMAP3: Remove unused board-types
>>>> OMAP3: Print correct silicon revision
>>> Applying all 3 patches I get
>>>
>>> sys_info.c: In function 'print_cpuinfo':
>>> sys_info.c:297: warning: no return statement in function returning
>>> non-void
>>> board.c: In function 'checkboard':
>>> board.c:349: warning: implicit declaration of function 'is_mem_sdr'
>>> board.c:357: warning: no return statement in function
>>> returning non-void
>>>
>> I usually do a distclean followed by make; but let me do this again.
>
> Yeah. found it... a miss in interactive commit 3/3.
>
> Should I re-submit the whole series?
> OR
> Is it okay to re-send just the last one.
I'm not a custodian, but last one marked with 'v4' should be
sufficient from my point of view.
Best regards
Dirk
> ~sanjeev
>
>> ~sanjeev
>>
>>> Not sure which patch it is, though.
>>>
>>> Best regards
>>>
>>> Dirk
>>>
>>> Btw.: You can easily check this by doing a
>>>
>>> ./MAKEALL ARM_CORTEX_A8
>>>
>>>
>>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>>
next prev parent reply other threads:[~2009-04-27 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 12:37 [U-Boot] [PATCHv3 0/3] OMAP3: Board specific updates Sanjeev Premi
2009-04-27 15:16 ` Dirk Behme
2009-04-27 15:18 ` Premi, Sanjeev
2009-04-27 15:26 ` Premi, Sanjeev
2009-04-27 15:39 ` Dirk Behme [this message]
2009-04-27 19:40 ` 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=49F5D1B5.8070603@googlemail.com \
--to=dirk.behme@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.