From: gerg@uclinux.org
To: linux-m68k@vger.kernel.org
Subject: [PATCH 0/2] m68k: propose move of platform coldfire
Date: Thu, 21 Aug 2014 13:04:05 +1000 [thread overview]
Message-ID: <1408590247-10875-1-git-send-email-gerg@uclinux.org> (raw)
Hi All,
I propose that we move the arch/m68k/platform/coldfire directory to be
directly under arch/m68k.
The current platform/ structure was inhereted from the move of m68knommu,
and is inconsistent with the existing m68k platforms (each having a
directory under arch/m68k).
Moving platform/coldfire is quite strait forward. The following patches do a
move, and fix up the broken pathname comments.
This does leave the question of what to do with the other directories still
under arch/m68k/platform, namely 68000 and 68360. Should they be moved in
the same way as coldfire?
Regards
Greg
next reply other threads:[~2014-08-21 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 3:04 gerg [this message]
2014-08-21 3:04 ` [PATCH 1/2] m68k: move coldfire platform code gerg
2014-08-21 3:04 ` [PATCH 2/2] m68k: fix crufty ColdFire intro comments gerg
2014-08-21 7:30 ` [PATCH 0/2] m68k: propose move of platform coldfire Geert Uytterhoeven
2014-08-21 11:47 ` Greg Ungerer
2014-08-21 13:32 ` Geert Uytterhoeven
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=1408590247-10875-1-git-send-email-gerg@uclinux.org \
--to=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.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