linux-kernel - Re: linux-next: Tree for April 24

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.0804240942300.10239@vixen.sonytel.be>
Date:	Thu, 24 Apr 2008 09:45:57 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: linux-next: Tree for April 24

	Hi Stephen,

On Thu, 24 Apr 2008, Stephen Rothwell wrote:
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next.  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.

For m68k, I've added multi_defconfig, to build a kernel for all supported m68k
platforms, excluding Sun 3 (Sun 3 kernels are incompatible with all other m68k
platforms).

Hence if you would build multi_defconfig and sun3_defconfig, you cover all of
our platforms and drivers.

Alternatively, you can just build all defconfigs, but that's more work ;-)

Thx for linux-next!

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/