From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Greg Ungerer <gerg@uclinux.org>,
linux-m68k@vger.kernel.org,
uClinux list <uclinux-dev@uclinux.org>
Subject: Re: m68k: Any plans to move over to arch/m68k/include?
Date: Tue, 25 Nov 2008 21:36:37 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0811252134180.1823@anakin> (raw)
In-Reply-To: <20081125201135.GB7128@uranus.ravnborg.org>
On Tue, 25 Nov 2008, Sam Ravnborg wrote:
> Almost all other architectures has moved over to arch/$ARCH/include
>
> Are you planning to do so for m68k for next merge window?
So far _I_ don't have those plans.
> Remaining ones: frv, h8300, m32r, m68k and mn10300
> The other are done or have patches queued for next merge window to do so.
>
> Can I be of any help?
However, m68k keeps working fine after `mv include/asm-m68k
arch/m68k/include/asm'. The problem is m68knommu, which includes header files
from m68k. The m68k and m68knommu headers have to be merged first, cfr. Arnd
Bergmann's comments and suggestions on linux-arch a while ago.
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
next prev parent reply other threads:[~2008-11-25 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 20:11 m68k: Any plans to move over to arch/m68k/include? Sam Ravnborg
2008-11-25 20:36 ` Geert Uytterhoeven [this message]
2008-11-29 13:21 ` Sam Ravnborg
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=Pine.LNX.4.64.0811252134180.1823@anakin \
--to=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=uclinux-dev@uclinux.org \
--cc=zippel@linux-m68k.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