From: Guenter Roeck <linux@roeck-us.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
Masahiro Yamada <masahiroy@kernel.org>,
Artur Rojek <contact@artur-rojek.eu>,
Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sh updates for v6.5
Date: Thu, 6 Jul 2023 08:08:00 -0700 [thread overview]
Message-ID: <3da1af1f-58e1-cb54-a959-1dfd6b8a1222@roeck-us.net> (raw)
In-Reply-To: <ab09d99c78bd378f23580427323c6418cd0888af.camel@physik.fu-berlin.de>
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
next prev parent reply other threads:[~2023-07-06 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 21:43 [GIT PULL] sh updates for v6.5 John Paul Adrian Glaubitz
2023-07-06 4:52 ` pr-tracker-bot
2023-07-06 14:01 ` Guenter Roeck
2023-07-06 14:04 ` John Paul Adrian Glaubitz
2023-07-06 15:08 ` Guenter Roeck [this message]
2023-07-06 15:19 ` John Paul Adrian Glaubitz
2023-07-06 15:16 ` Christoph Hellwig
2023-07-06 15:23 ` John Paul Adrian Glaubitz
2023-07-08 21:25 ` Sergey Shtylyov
2023-07-08 21:49 ` John Paul Adrian Glaubitz
2023-07-08 21:58 ` Artur Rojek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3da1af1f-58e1-cb54-a959-1dfd6b8a1222@roeck-us.net \
--to=linux@roeck-us.net \
--cc=contact@artur-rojek.eu \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=torvalds@linux-foundation.org \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox