From: Arnd Bergmann <arnd@arndb.de>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kbuild now support arch/$ARCH/include - time for ARCHs to convert
Date: Wed, 30 Jul 2008 09:07:24 +0200 [thread overview]
Message-ID: <200807300907.25186.arnd@arndb.de> (raw)
In-Reply-To: <48900EE4.8030606@snapgear.com>
On Wednesday 30 July 2008, Greg Ungerer wrote:
> I just tried moving the include/asm-m68knommu directory
> to arch/m68knommu/include/asm and it all worked fine.
> Clean compile first go :-) Nice. (As noted
> asm-offsets.h was still generated in incldue/asm-m68knommu
> afterwards though).
I think the more interesting aspect in m68knommu is what happens
when asm-m68k gets moved. Does that work as well?
I think the best way to deal with it is to remove all files
that just include an asm-m68k file with the same name, and
add -Iarch/m68k/include to your CFLAGS. Not sure about 'make
headers_install', if there is an easy way to install the
files from each of the two directories correctly.
Arnd <><
next prev parent reply other threads:[~2008-07-30 7:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 20:05 kbuild now support arch/$ARCH/include - time for ARCHs to convert Sam Ravnborg
2008-07-28 20:05 ` Sam Ravnborg
2008-07-29 3:06 ` Kyle McMartin
2008-07-29 3:06 ` Kyle McMartin
2008-07-29 3:27 ` Sam Ravnborg
2008-07-29 14:21 ` Kyle McMartin
2008-08-09 2:50 ` Sam Ravnborg
2008-07-30 6:49 ` Greg Ungerer
2008-07-30 7:07 ` Arnd Bergmann [this message]
2008-07-30 8:52 ` Sam Ravnborg
2008-07-30 9:34 ` David Howells
2008-07-30 12:26 ` Geert Uytterhoeven
2008-07-30 12:26 ` Geert Uytterhoeven
2008-07-31 3:23 ` Paul Mundt
2008-07-31 7:17 ` Geert Uytterhoeven
2008-07-31 11:26 ` Greg Ungerer
2008-07-31 11:26 ` Greg Ungerer
2008-07-31 19:47 ` Arnd Bergmann
2008-07-31 20:13 ` Sam Ravnborg
2008-08-01 7:35 ` Arnd Bergmann
2008-08-01 16:46 ` Sam Ravnborg
2008-07-30 8:38 ` Sam Ravnborg
2008-08-01 6:03 ` Greg Ungerer
2008-08-03 20:16 ` Geert Uytterhoeven
2008-08-04 0:34 ` Greg Ungerer
2008-08-04 5:10 ` Sam Ravnborg
2008-08-04 14:35 ` Arnd Bergmann
2008-08-04 16:00 ` Geert Uytterhoeven
2008-08-04 16:45 ` Sam Ravnborg
2008-07-31 18:23 ` Ralf Baechle
2008-07-31 20:14 ` Sam Ravnborg
2008-08-09 2:52 ` Sam Ravnborg
2008-08-09 3:09 ` Paul Mundt
2008-08-09 7:03 ` Sam Ravnborg
2008-08-09 7:20 ` Russell King
2008-08-09 11:13 ` Sam Ravnborg
2008-08-01 8:35 ` Martin Schwidefsky
2008-08-01 16:49 ` Sam Ravnborg
2008-08-05 4:18 ` Rusty Russell
2008-08-05 17:16 ` Geert Uytterhoeven
2008-08-05 17:16 ` Geert Uytterhoeven
2008-08-05 20:45 ` Sam Ravnborg
2008-08-05 22:06 ` Russell King
2008-08-06 19:21 ` Russell King
2008-08-06 19:28 ` Sam Ravnborg
2008-08-06 19:51 ` Russell King
2008-08-06 19:27 ` Sam Ravnborg
2008-08-09 7:28 ` 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=200807300907.25186.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gerg@snapgear.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).