From: Greg Ungerer <gerg@uclinux.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH 0/2] m68k: propose move of platform coldfire
Date: Thu, 21 Aug 2014 21:47:56 +1000 [thread overview]
Message-ID: <53F5DC6C.9070603@uclinux.org> (raw)
In-Reply-To: <CAMuHMdX2a4n3+wAOmF43NCSBKowJ6X72KDtjgKzW-vYCLGisbQ@mail.gmail.com>
Hi Geert,
On 21/08/14 17:30, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Thu, Aug 21, 2014 at 5:04 AM, <gerg@uclinux.org> wrote:
>> 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.
> That sounds fine to me.
>
>> 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?
> I think the 68*328 and 68360 SoC support can have their own directories,
> as these are platforms.
>
> However, these directories also contain 68000 and 68360 CPU support,
> which we may want to share with other platforms in the future, to support
> 68000-based Amigas, Ataris, Macs, Suns, ...
>
> But as that's a problem to fix when someone is working on it, it's fine
> for me to move these one level up, too.
Thanks for the feedback. I'll prepare patches that move these too then.
Regards
Greg
next prev parent reply other threads:[~2014-08-21 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 3:04 [PATCH 0/2] m68k: propose move of platform coldfire gerg
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 [this message]
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=53F5DC6C.9070603@uclinux.org \
--to=gerg@uclinux.org \
--cc=geert@linux-m68k.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