linux-kernel - Re: Build regressions/improvements in v3.8-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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1301072031540.18907@ayla.of.borg>
Date:	Mon, 7 Jan 2013 20:37:04 +0100 (CET)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: Build regressions/improvements in v3.8-rc2

On Mon, 7 Jan 2013, Geert Uytterhoeven wrote:
> JFYI, when comparing v3.8-rc2 to v3.8-rc1[3], the summaries are:
>   - build errors: +3/-3

3 regressions:
  + drivers/gpio/gpio-sx150x.c: error: field 'gpio_chip' has incomplete type: 47:35 => 47:35, 47:19
  + drivers/mfd/htc-i2cpld.c: error: field 'chip_in' has incomplete type: 55:26 => 55:19, 55:26
  + drivers/mfd/htc-i2cpld.c: error: field 'chip_out' has incomplete type: 51:26 => 51:26, 51:19

I guess these are just new fallout from the two bogus "selects GPIOLIB" in
SSB/BCMA, pulling in all GPIO drivers on platforms that don't support it,
for which I posted two patches a while ago:
    https://lkml.org/lkml/2012/12/16/68
    https://lkml.org/lkml/2012/12/16/69

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/