mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: kbuild <linux-kbuild@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH 01/14] kbuild: search arch/$ARCH/include before include/
Date: Sun, 18 Oct 2009 10:15:10 +0200	[thread overview]
Message-ID: <1255853723-477-1-git-send-email-sam@ravnborg.org> (raw)
In-Reply-To: <20091018080635.GA13767@merkur.ravnborg.org>

The namespace used in arch/$ARCH/include is different from
what is used in include/ except for the include/asm directory.

This patch gives the arch/$ARCH/include/asm directory priority
over include/asm.

When we add asm-offsets.h to arch/$ARCH/include/asm/ this
patch makes sure we pick up the arch specific version
and not the one we have in include/asm.

The situation with an asm-offsets.h file located in
both include/asm _and_ arch/$ARCH/include/asm will happen
when we move more files over to include/generated.

This happens because in some cases it is not practical
to rename all users so we simply add a file
in arch/$ARCH/include/asm that includes the generated version.

This is the solution we use for asm-offsets.h as an example.

Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
---
 Makefile |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 9425d1d..a805f5c 100644
--- a/Makefile
+++ b/Makefile
@@ -334,9 +334,8 @@ CFLAGS_GCOV	= -fprofile-arcs -ftest-coverage
 
 # Use LINUXINCLUDE when you must reference the include/ directory.
 # Needed to be compatible with the O= option
-LINUXINCLUDE    := -Iinclude \
+LINUXINCLUDE    := -I$(srctree)/arch/$(hdr-arch)/include -Iinclude \
                    $(if $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include) \
-                   -I$(srctree)/arch/$(hdr-arch)/include               \
                    -include include/linux/autoconf.h
 
 KBUILD_CPPFLAGS := -D__KERNEL__
-- 
1.6.2.5


  reply	other threads:[~2009-10-18  8:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  8:06 [PATCH 0/14 v2] kbuild: Move files to include/generated Sam Ravnborg
2009-10-18  8:15 ` Sam Ravnborg [this message]
2009-10-18  8:15 ` [PATCH 02/14] dontdiff: add generated Sam Ravnborg
2009-10-18  8:15 ` [PATCH 03/14] kbuild: move bounds.h to include/generated Sam Ravnborg
2009-10-18  8:15 ` [PATCH 04/14] kbuild: move asm-offsets.h " Sam Ravnborg
2009-10-18  8:15 ` [PATCH 05/14] ia64: move nr-irqs.h " Sam Ravnborg
2009-10-18  8:15 ` [PATCH 06/14] arm: move mach-types " Sam Ravnborg
2009-10-18  8:15 ` [PATCH 07/14] sh: move machtypes.h " Sam Ravnborg
2009-10-18  8:15 ` [PATCH 08/14] kbuild: drop include2/ used for O=... builds Sam Ravnborg
2009-10-18  8:15 ` [PATCH 09/14] kbuild: do not check for include/asm-$ARCH Sam Ravnborg
2009-10-18  8:15 ` [PATCH 10/14] kbuild: drop include/asm Sam Ravnborg
2009-10-18  8:15 ` [PATCH 11/14] kbuild: move compile.h to include/generated Sam Ravnborg
2009-10-18  8:15 ` [PATCH 12/14] drop explicit include of autoconf.h Sam Ravnborg
2009-10-18  8:15 ` [PATCH 13/14] kbuild: move autoconf.h to include/generated Sam Ravnborg
2009-11-25 14:28   ` Michal Marek
2009-10-18  8:15 ` [PATCH 14/14] kbuild: move utsrelease.h " 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=1255853723-477-1-git-send-email-sam@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

Powered by JetHome