U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:16:33 +0200	[thread overview]
Message-ID: <49F5CC51.9070607@googlemail.com> (raw)
In-Reply-To: <1240835830-23646-1-git-send-email-premi@ti.com>

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

Not sure which patch it is, though.

Best regards

Dirk

Btw.: You can easily check this by doing a

./MAKEALL ARM_CORTEX_A8

  reply	other threads:[~2009-04-27 15:16 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 [this message]
2009-04-27 15:18   ` Premi, Sanjeev
2009-04-27 15:26     ` Premi, Sanjeev
2009-04-27 15:39       ` Dirk Behme
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=49F5CC51.9070607@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox