linux-kernel - Re: next build: 143 builds: 1 failed, 142 passed, 1 error, 22 warnings (next-20160801)

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: <CAMuHMdWqDQNBATgSxmL=ma3uQqr6A_-STCbXoD1nPyF1FAGUDQ@mail.gmail.com>
Date:	Thu, 4 Aug 2016 16:58:40 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	George Spelvin <linux@...encehorizons.net>
Cc:	Arnd Bergmann <arnd@...db.de>, bot@...nelci.org,
	kernel-build-reports@...ts.linaro.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: next build: 143 builds: 1 failed, 142 passed, 1 error, 22
 warnings (next-20160801)

Hi Georges,

On Thu, Aug 4, 2016 at 4:49 PM, George Spelvin
<linux@...encehorizons.net> wrote:
>> As these patches were meant for generic non-m68k code, I didn't plan
>> to take them through my tree.
>
> Well, that explains everything.  Sorry for letting it fall through the
> cracks.  I assumed that since you send pull requests to Linus regularly,
> you'd send it directly.
>
> That's why I only acked the patch rather than did anything with it.
>
> So, who wants to send it now?

I think you should queue them in your git tree, and send a pull request
to Linus, as that's how the original code went upstream.

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