From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH-OMAP3] OMAP3: Clean up board files
Date: Thu, 20 Nov 2008 23:38:52 +0100 [thread overview]
Message-ID: <20081120223852.GL20436@game.jcrosoft.org> (raw)
In-Reply-To: <491e86c4.0b38560a.415d.0169@mx.google.com>
On 09:22 Sat 15 Nov , dirk.behme at googlemail.com wrote:
> - Use readx/writex instead of direct pointer access
> - Replace hardcoded values by macros
> - Minor space to tab conversion
>
> No functional change.
>
> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>
> ---
> board/omap3/beagle/beagle.c | 78 +++++++++++++++++++-------------
> board/omap3/overo/overo.c | 90 ++++++++++++++++++++++---------------
> include/asm-arm/arch-omap3/omap3.h | 70 ++++++++++++++++++++++++++++
> 3 files changed, 171 insertions(+), 67 deletions(-)
>
apply to u-boot-arm/omap3
prev parent reply other threads:[~2008-11-20 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 8:22 [U-Boot] [PATCH-OMAP3] OMAP3: Clean up board files dirk.behme at googlemail.com
2008-11-20 22:38 ` Jean-Christophe PLAGNIOL-VILLARD [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=20081120223852.GL20436@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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