linux-kernel - Re: linux-next: m68k build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080801204157.GA12390@uranus.ravnborg.org>
Date:	Fri, 1 Aug 2008 22:41:57 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	David Miller <davem@...emloft.net>, linux-next@...r.kernel.org,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...r.kernel.org>
Subject: Re: linux-next: m68k build failure

On Fri, Aug 01, 2008 at 03:52:22PM +0200, Geert Uytterhoeven wrote:
> 	Hi Stephen,
> 
> On Fri, 1 Aug 2008, Stephen Rothwell wrote:
> > On Wed, 30 Jul 2008 10:49:35 +0200 Sam Ravnborg <sam@...nborg.org> wrote:
> > >
> > > Full list of relevant files:
> > > include/asm-m68k/contregs.h:#include <asm-sparc/contregs.h>
> > > include/asm-m68k/fbio.h:#include <asm-sparc/fbio.h>
> > > include/asm-m68k/idprom.h:#include <asm-sparc/idprom.h>
> > 
> > I applied the following patch to today's linux-next.
> 
> Thanks!
> 
> 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.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/