linux-kernel - Re: Build regressions/improvements in v4.18-rc7

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]

Date:   Wed, 1 Aug 2018 14:24:04 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Martin Sebor <msebor@...il.com>
Subject: Re: Build regressions/improvements in v4.18-rc7

Hi Geert,

On Wed, Aug 1, 2018 at 8:56 AM, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Hi Miguel,
>
> On Mon, Jul 30, 2018 at 6:05 PM Miguel Ojeda
> <miguel.ojeda.sandonis@...il.com> wrote:
>> On Mon, Jul 30, 2018 at 8:46 AM, Geert Uytterhoeven
>> <geert@...ux-m68k.org> wrote:
>> > Below is the list of build error/warning regressions/improvements in
>> > v4.18-rc7[1] compared to v4.17[2].
>
>> Also, a suggestion for Geert (or whoever is maintaining the bot): it
>> would be nice to see from which target the warnings are exactly coming
>> from. Many/most warnings come from many/most targets, but at least
>> knowing 1 of them would be nice.
>
> I used to upload the summaries containing that information to kernel.org,
> but stopped doing so when kup was introduced (and I had to spend time to
> learn how to use kup).
>
> I've attached the summary for v4.18-rc7.

Thanks!

Cheers,
Miguel

>
> 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