From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: [PATCH 00/11] m68knommu: remove ColdFire sub-architecture directories
Date: Wed, 2 May 2012 11:08:55 +1000 [thread overview]
Message-ID: <1335920946-11297-1-git-send-email-gerg@snapgear.com> (raw)
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(-)
next reply other threads:[~2012-05-02 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 1:08 gerg [this message]
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
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=1335920946-11297-1-git-send-email-gerg@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@vger.kernel.org \
--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