linux-kernel - Re: [GIT PULL] GPIO bulk changes for v3.14

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 22 Jan 2014 09:12:00 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Lars Poeschel <poeschel@...onage.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [GIT PULL] GPIO bulk changes for v3.14

On Wed, Jan 22, 2014 at 8:54 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
>> The fact that it doesn't even compile makes me doubt your statement
>> that it has been in linux-next. It doesn't even pass a basic
>> allmodconfig build.
>
> Hm I rely on the zeroday build, and didn't get any angry compile errors.
> I'll double-check with Fengguang to see what's going on here and
> that branches get proper buildtesting.

There may be some delay. Sometimes it's a few hours, but last week I got an
email about a build failure I had in one of my branches since at least v3.9.

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/