From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.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: Sat, 29 Nov 2008 14:21:23 +0100 [thread overview]
Message-ID: <20081129132123.GA13985@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0811252134180.1823@anakin>
On Tue, Nov 25, 2008 at 09:36:37PM +0100, Geert Uytterhoeven wrote:
> 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.
This one (and the thread following it)
http://marc.info/?l=linux-arch&m=121753383713553&w=2
I agree this is the correct approach.
Looks reasonable simple to do for anyone having the relevant toolchains
and assuming only few pending patches in this area.
I do not have time to do it for now :-(
Sam
prev parent reply other threads:[~2008-11-29 13:24 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
2008-11-29 13:21 ` Sam Ravnborg [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=20081129132123.GA13985@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.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