From: Greg Ungerer <gerg@snapgear.com>
To: Luis Alves <ljalvs@gmail.com>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 00/11] m68knommu: remove ColdFire sub-architecture directories
Date: Thu, 3 May 2012 00:07:50 +1000 [thread overview]
Message-ID: <4FA13FB6.6020806@snapgear.com> (raw)
In-Reply-To: <CAGj5WxB2f-4UHK-x=SESX4QqnbfsL0i=LhXoOOZeK2cFhDiQhg@mail.gmail.com>
Hi Luis,
On 05/02/2012 07:50 PM, Luis Alves wrote:
> I've done a similar thing for the 68000 cpu's. Ended up with a single
> platform/68000 directory and removed the 68328, 68EZ328 and 68VZ328
> directories.
That sounds great.
> When I have the time I'll prepare the patches and send them (probably
> latter today).
Looking forward to them :-)
> I'm not sure if anyone is still building 3.x kernels for the 68[xx]328
> SoC's but would be nice if someone could test building the kernel for
> the boards using those chips (hopefully I didn't break up anything).
> For the 68000 (and my board) it's working good.
I build them occasionally, but I don't have any way to test any
of those targets.
Regards
Greg
> On Wed, May 2, 2012 at 2:08 AM,<gerg@snapgear.com> wrote:
>>
>> Currently the different ColdFire sub-archiectures are split up with a
>> directory for each family type. Most though only contain a small amount
>> of code, it just doesn't seem to make any sense to keep them separate.
>>
>> Move all the ColdFire sub-architecture code into the platform/coldfire
>> directory, and remove the sub-architecture directories. We already build
>> the common ColdFire components based on sub-architecture type anyway,
>> so there is very little Makefile change required.
>>
>> Overall we remove about 200 lines of duplicated Makefile code, and end
>> up with all the ColdFire specific code in a single directory.
>>
>> ---
>>
>> áarch/m68k/Makefile á á á á á á á á á á | á 10 ----------
>> áarch/m68k/platform/5206/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/520x/Makefile á á á | á 17 -----------------
>> áarch/m68k/platform/523x/Makefile á á á | á 17 -----------------
>> áarch/m68k/platform/5249/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/5272/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/527x/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/528x/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/5307/Makefile á á á | á 20 --------------------
>> áarch/m68k/platform/532x/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/5407/Makefile á á á | á 18 ------------------
>> áarch/m68k/platform/54xx/Makefile á á á | á 19 -------------------
>> áarch/m68k/platform/coldfire/Makefile á | á 24 ++++++++++++++----------
>> áb/arch/m68k/Makefile á á á á á á á á á | á á2 --
>> áb/arch/m68k/platform/coldfire/Makefile | á á4 ++--
>> áb/arch/m68k/platform/coldfire/m5206.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m520x.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m523x.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m5249.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m5272.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m527x.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m528x.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m532x.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m5407.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/m54xx.c á| á á1 -
>> áb/arch/m68k/platform/coldfire/nettel.c | á á1 -
>> á26 files changed, 16 insertions(+), 234 deletions(-)
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at áhttp://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2012-05-02 14:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 1:08 [PATCH 00/11] m68knommu: remove ColdFire sub-architecture directories gerg
2012-05-02 1:08 ` [PATCH 01/11] m68knommu: move the 5206 platform code into the common ColdFire code directory gerg
2012-05-02 1:08 ` [PATCH 02/11] m68knommu: move the 520x " gerg
2012-05-02 1:08 ` [PATCH 03/11] m68knommu: move the 523x " gerg
2012-05-02 1:08 ` [PATCH 04/11] m68knommu: move the 5249 " gerg
2012-05-02 1:09 ` [PATCH 05/11] m68knommu: move the 5272 " gerg
2012-05-02 1:09 ` [PATCH 06/11] m68knommu: move the 527x " gerg
2012-05-02 1:09 ` [PATCH 07/11] m68knommu: move the 528x " gerg
2012-05-02 1:09 ` [PATCH 08/11] m68knommu: move the 5307 " gerg
2012-05-02 1:09 ` [PATCH 09/11] m68knommu: move the 5407 " gerg
2012-05-02 1:09 ` [PATCH 10/11] m68knommu: move the 532x " gerg
2012-05-02 1:09 ` [PATCH 11/11] m68knommu: move the 54xx " gerg
2012-05-02 9:16 ` [PATCH 00/11] m68knommu: remove ColdFire sub-architecture directories Geert Uytterhoeven
2012-05-02 9:47 ` Greg Ungerer
2012-05-02 9:50 ` Luis Alves
2012-05-02 14:07 ` Greg Ungerer [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=4FA13FB6.6020806@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@vger.kernel.org \
--cc=ljalvs@gmail.com \
--cc=uclinux-dev@uclinux.org \
/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