From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] OMAP3: igep00x0: rename config file to omap3_igep00x0.h
Date: Thu, 19 Sep 2013 18:00:37 +0300 [thread overview]
Message-ID: <523B1195.5@compulab.co.il> (raw)
In-Reply-To: <CABxcv==SK4U4R07kQ79gwEbiCyByLGPNMiueZmpwpyfVXdW=WA@mail.gmail.com>
Hi Javier,
On 09/19/2013 04:04 PM, Javier Martinez Canillas wrote:
> On Mon, Sep 2, 2013 at 1:52 PM, Enric Balletbo Serra
> <eballetbo@gmail.com> wrote:
>> 2013/9/2 Javier Martinez Canillas <javier@dowhile0.org>:
>>> There seems to be a naming convention for the configuration
>>> files for boards using the same SoC family. This makes
>>> easier to do changes that affect different boards based
>>> on the same SoC.
>>>
>>> Since the IGEPv2 board and the IGEP COM Module use a TI
>>> OMAP35xx/DM37xx processor, is better to rename its board
>>> config to use this naming scheme.
>>>
>>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>>> ---
>>>
>>> Changes since v1:
>>> - Fix some issues in the commit changelog pointed out by Enric Balletbo.
>>>
>>> boards.cfg | 10 +-
>>> include/configs/igep00x0.h | 370 ---------------------------------------
>>> include/configs/omap3_igep00x0.h | 370 +++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 375 insertions(+), 375 deletions(-)
>>> delete mode 100644 include/configs/igep00x0.h
>>> create mode 100644 include/configs/omap3_igep00x0.h
>>>
>>> diff --git a/boards.cfg b/boards.cfg
>>> index d717226..8f1cb6e 100644
>>> --- a/boards.cfg
>>> +++ b/boards.cfg
>>> @@ -297,11 +297,11 @@ omap3_overo arm armv7 overo -
>>> omap3_pandora arm armv7 pandora - omap3
>>> dig297 arm armv7 dig297 comelit omap3
>>> cm_t35 arm armv7 cm_t35 compulab omap3
>>> -igep0020 arm armv7 igep00x0 isee omap3 igep00x0:MACH_TYPE=MACH_TYPE_IGEP0020,BOOT_ONENAND
>>> -igep0020_nand arm armv7 igep00x0 isee omap3 igep00x0:MACH_TYPE=MACH_TYPE_IGEP0020,BOOT_NAND
>>> -igep0030 arm armv7 igep00x0 isee omap3 igep00x0:MACH_TYPE=MACH_TYPE_IGEP0030,BOOT_ONENAND
>>> -igep0030_nand arm armv7 igep00x0 isee omap3 igep00x0:MACH_TYPE=MACH_TYPE_IGEP0030,BOOT_NAND
>>> -igep0032 arm armv7 igep00x0 isee omap3 igep00x0:MACH_TYPE=MACH_TYPE_IGEP0032,BOOT_ONENAND
>>> +omap3_igep0020 arm armv7 igep00x0 isee omap3 omap3_igep00x0:MACH_TYPE=MACH_TYPE_IGEP0020,BOOT_ONENAND
>>> +omap3_igep0020_nand arm armv7 igep00x0 isee omap3 omap3_igep00x0:MACH_TYPE=MACH_TYPE_IGEP0020,BOOT_NAND
>>> +omap3_igep0030 arm armv7 igep00x0 isee omap3 omap3_igep00x0:MACH_TYPE=MACH_TYPE_IGEP0030,BOOT_ONENAND
>>> +omap3_igep0030_nand arm armv7 igep00x0 isee omap3 omap3_igep00x0:MACH_TYPE=MACH_TYPE_IGEP0030,BOOT_NAND
>>> +omap3_igep0032 arm armv7 igep00x0 isee omap3 omap3_igep00x0:MACH_TYPE=MACH_TYPE_IGEP0032,BOOT_ONENAND
>>> am335x_igep0033 arm armv7 igep0033 isee am33xx
>>> am3517_evm arm armv7 am3517evm logicpd omap3
>>> mt_ventoux arm armv7 mt_ventoux teejet omap3
>
>> Acked-by: Enric Balletbo i Serra <eballetbo@iseebcn.com>
>
> These patches don't apply on master anymore after commit 27af930e9
> ("Merge and reformat boards.cfg and MAINTAINERS"). I'll rebase the
> patches and repost.
If you are about to repost, can you please add '-M' flag to
git format-patch command (if you use this command).
This will detect renames and lower the patch size...
--
Regards,
Igor
next prev parent reply other threads:[~2013-09-19 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:04 [U-Boot] [PATCH v2 1/2] ARM: IGEP0033: rename config file to am335x_igep0033.h Javier Martinez Canillas
2013-09-02 8:04 ` [U-Boot] [PATCH v2 2/2] OMAP3: igep00x0: rename config file to omap3_igep00x0.h Javier Martinez Canillas
2013-09-02 11:52 ` Enric Balletbo Serra
2013-09-19 13:04 ` Javier Martinez Canillas
2013-09-19 15:00 ` Igor Grinberg [this message]
2013-09-19 15:13 ` Javier Martinez Canillas
2013-09-19 15:14 ` Javier Martinez Canillas
2013-09-02 11:51 ` [U-Boot] [PATCH v2 1/2] ARM: IGEP0033: rename config file to am335x_igep0033.h Enric Balletbo Serra
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=523B1195.5@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 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.