From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv4 0/3] OMAP3: Board specific updates
Date: Thu, 30 Apr 2009 20:42:33 +0200 [thread overview]
Message-ID: <49F9F119.2070004@googlemail.com> (raw)
In-Reply-To: <49F5D98D.7000602@googlemail.com>
Dirk Behme wrote:
> 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.
>>
>> This series fixes the compile warning
>> pointed by Dirk Behme.
>>
>> 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
>
> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
> Tested-by: Dirk Behme <dirk.behme@googlemail.com>
It doesn't really bothers me, but would have been nice if something
like this would have found its way into git.
Dirk
prev parent reply other threads:[~2009-04-30 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 15:56 [U-Boot] [PATCHv4 0/3] OMAP3: Board specific updates Sanjeev Premi
2009-04-27 16:13 ` Dirk Behme
2009-04-30 18:42 ` Dirk Behme [this message]
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=49F9F119.2070004@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