linux-kernel - Re: [GIT PULL] sh updates for v6.5

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: <3da1af1f-58e1-cb54-a959-1dfd6b8a1222@roeck-us.net>
Date:   Thu, 6 Jul 2023 08:08:00 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Sergey Shtylyov <s.shtylyov@....ru>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Artur Rojek <contact@...ur-rojek.eu>,
        Rich Felker <dalias@...c.org>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        linux-sh@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] sh updates for v6.5

On 7/6/23 07:04, John Paul Adrian Glaubitz wrote:
> On Thu, 2023-07-06 at 07:01 -0700, Guenter Roeck wrote:
>> Perfect example why it is a bad idea to let build failures linger around.
>> The build failure fixed by this patch ...
> 
> How was that lingered around? Your patch was merged within less than a week.
> 

The _build failure_ was lingering around, not my fix for it.

>>> John Paul Adrian Glaubitz (1):
>>>         sh: j2: Use ioremap() to translate device tree address into kernel memory
>>>
>>> Masahiro Yamada (4):
>>>         sh: Fix -Wmissing-include-dirs warnings for various platforms
>>>         sh: Move build rule for cchips/hd6446x/ to arch/sh/Kbuild
>>>         sh: Refactor header include path addition
>>>         sh: Remove compiler flag duplication
>>>
>>> Sergey Shtylyov (1):
>>>         sh: Avoid using IRQ0 on SH3 and SH4
>>>
>> ... was hiding boot failures with all my qemu emulations caused by
>> this patch.
> 
> But Sergey's patch had been in my for-next tree since June 11 [1].
> 

The build failure was introduced into linux-next with commit 99b619b37ae1.
According to the commit log, that happened around June 9. Ever since then
all sh builds in linux-next failed.

Guenter