From: Sam Ravnborg <sam@ravnborg.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: New location for generic headers?
Date: Wed, 3 Dec 2008 13:01:10 +0100 [thread overview]
Message-ID: <20081203120110.GA2822@uranus.ravnborg.org> (raw)
In-Reply-To: <200812031140.02338.arnd@arndb.de>
On Wed, Dec 03, 2008 at 11:40:01AM +0100, Arnd Bergmann wrote:
> On Wednesday 03 December 2008, Andi Kleen wrote:
> > Clean up namespace in kmap_types.h
> >
> > During debugging I often use custom "D" macros. But I ran
> > into a name space conflict with kmap_types.h which also defines a D macro.
> > Rename the kmap_types.h one to KMAPD.
> >
> > No semantical changes.
> >
> > Signed-off-by: Andi Kleen <ak@linux.intel.com>
>
> The patch looks ok, but it seems wrong to do this only on one architecture,
> because kmap_types.h is mostly identical across all architectures.
>
> I'm working on patches to consolidate a lot of generic headers, why not
> add this in a generic way and make x86 use that version?
Should we try to get rid of all those silly:
#include <asm-generic/foo.h>
files we have in arch/$ARCH/include/asm?
We could for example add include/generic/ last in the search path.
Or we could add the files in include/asm and add that last in the
search path.
Then if we do not find <asm/foo.h> in arch/$ARCH/include/asm/
then we search include/asm.
Before we can do this we need to get rid of the last users of
include/asm-$ARCH - but we are almost there.
Only m68k seems to require some effort.
Sam
next prev parent reply other threads:[~2008-12-03 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 0:36 [PATCH] Clean up namespace in kmap_types.h Andi Kleen
2008-12-03 10:40 ` Arnd Bergmann
2008-12-03 11:20 ` Andi Kleen
2008-12-03 12:13 ` Arnd Bergmann
2008-12-03 12:01 ` Sam Ravnborg [this message]
2008-12-03 12:19 ` New location for generic headers? Andi Kleen
2008-12-03 12:21 ` Christoph Hellwig
2008-12-03 12:42 ` Andi Kleen
2008-12-03 12:37 ` Christoph Hellwig
2008-12-03 12:26 ` Arnd Bergmann
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=20081203120110.GA2822@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox