From: Geert Uytterhoeven <geert@linux-m68k•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Sam Ravnborg <sam@ravnborg•org>,
David Miller <davem@davemloft•net>,
linux-next@vger•kernel.org,
Linux Kernel Development <linux-kernel@vger•kernel.org>,
Linux/m68k <linux-m68k@vger•kernel.org>
Subject: Re: linux-next: m68k build failure
Date: Sun, 3 Aug 2008 22:00:55 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808032200190.23329@anakin> (raw)
In-Reply-To: <20080802140650.ed81402d.sfr@canb.auug.org.au>
On Sat, 2 Aug 2008, Stephen Rothwell wrote:
> On Fri, 1 Aug 2008 22:41:57 +0200 Sam Ravnborg <sam@ravnborg•org> wrote:
> > On Fri, Aug 01, 2008 at 03:52:22PM +0200, Geert Uytterhoeven wrote:
> > > BTW, is there a (good) way to have this without duplicating those header files?
> >
> > The only solution I can come up with right now is:
> >
> > Makefile:
> > ccflags-y += -Iarch/sparc/include
> >
> > foo.c:
> > #include <asm/fbio.h>
> >
> > Disadvantage is that we loose the explicit documentation that this
> > is header files from another architecture.
> > So we should at least add a comment saying this.
> >
> > And the above would not work if the file has same filename,
> > but then that is not a likely situation either.
>
> There is at least one of the m68k header files that includes the sparc
> file of the same name and then does other stuff. So this scheme would
> not cover that (unless we used #include_next?)
OK, so I'll take Stephen's patch (thanks!) and send it to Linus.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-08-03 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 7:52 linux-next: m68k build failure Stephen Rothwell
2008-07-30 7:54 ` Stephen Rothwell
2008-07-30 8:02 ` David Miller
2008-07-30 8:49 ` Sam Ravnborg
2008-08-01 5:37 ` Stephen Rothwell
2008-08-01 13:52 ` Geert Uytterhoeven
2008-08-01 20:41 ` Sam Ravnborg
2008-08-02 4:06 ` Stephen Rothwell
2008-08-03 20:00 ` Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 6:50 Stephen Rothwell
2008-08-28 6:59 ` Ingo Molnar
2008-12-09 6:45 Stephen Rothwell
2008-12-09 8:00 ` David Miller
2008-12-09 8:50 ` Stephen Rothwell
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=Pine.LNX.4.64.0808032200190.23329@anakin \
--to=geert@linux-m68k$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-m68k@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sam@ravnborg$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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