From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Ungerer <gerg@uclinux.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 15:32:51 +0200 [thread overview]
Message-ID: <CAMuHMdUFoGEUw7Sy2Nx4gR70GrxVYgJXPwL_eFnpS3CcybXigw@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdX2a4n3+wAOmF43NCSBKowJ6X72KDtjgKzW-vYCLGisbQ@mail.gmail.com>
On Thu, Aug 21, 2014 at 9:30 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> 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.
All 2 of this series:
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2014-08-21 13:32 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
2014-08-21 13:32 ` Geert Uytterhoeven [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=CAMuHMdUFoGEUw7Sy2Nx4gR70GrxVYgJXPwL_eFnpS3CcybXigw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.