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: <Pine.LNX.4.64.0808011551120.30950@anakin>
Date:	Fri, 1 Aug 2008 15:52:22 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	Sam Ravnborg <sam@...nborg.org>,
	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

	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?

I hope to move to arch/m68k/include soon, too.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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
--
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/