From: Greg Ungerer <gerg@snapgear.com>
To: torvalds@linux-foundation.org
Cc: gerg@uclinux.org, linux-kernel@vger.kernel.org
Subject: [M68KNOMMU 00/06]: move common ColdFire code to its own directory
Date: Fri, 1 Feb 2008 17:37:08 +1000 [thread overview]
Message-ID: <200802010737.m117b8EL022685@goober> (raw)
Move common ColdFire CPU code into its own platform directory.
Currently the common ColdFire CPU family code sits in the
arch/m68knommu/platform/5307 directory. This is confusing, the files
containing this common code are in no way specific to the 5307 ColdFire.
Create an arch/m68knommu/platform/coldfire directory to contain this
common code. Other m68knommu CPU varients do not need use this code
though, so it doesn't make sense to move it to arch/m68knommu/kernel.
Signed-off-by: Greg Ungerer <gerg@uclinux.org
Makefile | 22 ++--
platform/5307/Makefile | 14 --
platform/5307/entry.S | 235 -------------------------------------------- platform/5307/head.S | 222 -----------------------------------------
platform/5307/pit.c | 97 ------------------
platform/5307/timers.c | 155 -----------------------------
platform/5307/vectors.c | 105 -------------------
platform/coldfire/Makefile | 32 +++++
platform/coldfire/dma.c | 39 +++++++
platform/coldfire/entry.S | 235 ++++++++++++++++++++++++++++++++++++++++++++ platform/coldfire/head.S | 222 +++++++++++++++++++++++++++++++++++++++++
platform/coldfire/pit.c | 97 ++++++++++++++++++
platform/coldfire/timers.c | 155 +++++++++++++++++++++++++++++
platform/coldfire/vectors.c | 105 +++++++++++++++++++
14 files changed, 897 insertions(+), 838 deletions(-)
reply other threads:[~2008-02-01 7:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200802010737.m117b8EL022685@goober \
--to=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®