From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] OMAP3: use a single board file for IGEP devices
Date: Thu, 27 Dec 2012 15:19:12 +0200 [thread overview]
Message-ID: <50DC4AD0.70102@compulab.co.il> (raw)
In-Reply-To: <1356608156-29339-1-git-send-email-javier.martinez@collabora.co.uk>
On 12/27/12 13:35, Javier Martinez Canillas wrote:
> Even when the IGEPv2 board and the IGEP Computer-on-Module
> are different from a form factor point of view, they are
> very similar in the fact that share many components and how
> they are wired.
>
> So, it is possible (and better) to have a single board file
> for both devices and just use the CONFIG_MACH_TYPE to make
> a differentiation between each board when needed.
>
> This change avoids code duplication by removing 298 lines of
> code and makes future maintenance easier.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Acked-by: Igor Grinberg <grinberg@compulab.co.il>
--
Regards,
Igor.
next prev parent reply other threads:[~2012-12-27 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 11:35 [U-Boot] [PATCH v2 1/2] OMAP3: use a single board file for IGEP devices Javier Martinez Canillas
2012-12-27 13:19 ` Igor Grinberg [this message]
2013-01-25 22:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
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=50DC4AD0.70102@compulab.co.il \
--to=grinberg@compulab.co.il \
--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