linux-kernel - Re: linux-next: triage for March 14, 2012

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: <CAMuHMdV45SBg+cm0+x07SfvY-xpjqb_ZVznn-vD=70G1YZXnFw@mail.gmail.com>
Date:	Thu, 15 Mar 2012 09:00:50 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: triage for March 14, 2012

On Thu, Mar 15, 2012 at 00:39, Paul Gortmaker
<paul.gortmaker@...driver.com> wrote:
> New breakage since last report:

Seems you missed two new failures for m68k/allmodconfig:

include/linux/mmc/core.h:128:20: error: field 'completion' has incomplete type
make[4]: *** [drivers/mmc/card/mmc_test.o] Error 1

drivers/staging/android/persistent_ram.c:457:2: error: implicit
declaration of function 'memblock_reserve'
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [drivers/staging/android/persistent_ram.o] Error 1

> m68k:allmodconfig
>       when:   Mar 9, 00:38
>       why:    ERROR: "__udivdi3" [drivers/media/dvb/frontends/rtl2830.ko] undefined!

This seems to be fixed, unless it doesn't get that far anymore.

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/