linux-kernel - Re: Build regressions/improvements in v2.6.37-rc2

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: <AANLkTi=NTGOv+EF_y=__=+P1ud7vqjvoaELPNi6ZhqbE@mail.gmail.com>
Date:	Wed, 17 Nov 2010 20:32:15 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Michael Ellerman <michael@...erman.id.au>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: Build regressions/improvements in v2.6.37-rc2

On Wed, Nov 17, 2010 at 20:28, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v2.6.37-rc2[1] compared to v2.6.36[2].

> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/head/3363/ (97 out of 108 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/head/3461/ (75 out of 108 configs)

Would it be possible to make sure tagged versions are always built for
all 108 configs?
Currently the coverage depends on how soon Linus pushes a new commit.

Thanks!

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/