From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
jdike@addtoit.com
Subject: Re: asm-offsets.h is generated in the source tree
Date: Mon, 12 Sep 2005 00:16:01 +0100 [thread overview]
Message-ID: <20050911231601.GL25261@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20050911220328.GE2177@mars.ravnborg.org>
On Mon, Sep 12, 2005 at 12:03:28AM +0200, Sam Ravnborg wrote:
> If the kernel had used a scheme like the following everything could be
> solved by a few -I statements:
>
> include/i386/asm/<what we have in include/asm-i386 today>
> include/ia64/asm/<what we have in include/asm-ia64 today>
> etc.
>
> Then to use ia64 we would just use:
> -Iinclude/ia64
Doesn't solve the problem. We have header pulled from include/linux/*
by asm/foo.h. It contains generic UML stuff _and_ include of regular
asm/foo.h _of_ _the_ _subarch_. Not a UML stuff that varies depending
on the subarch; we want whatever normal i386, amd64, etc. kernel would
get upon include of asm/foo.h.
See what I mean? _IF_ we just wanted subarch foo.h, your scheme would
work. If we wanted subarch-dependent header that would be pulled by
foo.h - ditto (sysdep/blah.h from foo.h). But we can't do that when
we want #include <asm/foo.h> (from arch-independent code) pull some
UML stuff *and* asm/foo.h of subarch.
That's the problem. Everything else is reasonably easy to deal with.
That one is not. And yes, I know about #include_next. I'd rather
stick to C, though, TYVM...
next prev parent reply other threads:[~2005-09-11 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 15:20 asm-offsets.h is generated in the source tree Stephen Rothwell
2005-09-10 16:19 ` Sam Ravnborg
2005-09-11 2:32 ` Al Viro
2005-09-11 8:31 ` Sam Ravnborg
2005-09-11 15:45 ` Al Viro
2005-09-11 17:04 ` Sam Ravnborg
2005-09-11 21:29 ` Al Viro
2005-09-11 22:03 ` Sam Ravnborg
2005-09-11 23:16 ` Al Viro [this message]
2005-09-12 19:15 ` Sam Ravnborg
2005-09-13 6:30 ` Al Viro
2005-09-13 6:48 ` Kyle Moffett
2005-09-13 6:53 ` Keith Owens
2005-09-13 6:58 ` Kyle Moffett
2005-09-13 21:55 ` Al Viro
2005-09-15 1:07 ` Al Viro
2005-09-10 19:08 ` 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=20050911231601.GL25261@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.