[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab09d99c78bd378f23580427323c6418cd0888af.camel@physik.fu-berlin.de>
Date: Thu, 06 Jul 2023 16:04:45 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Guenter Roeck <linux@...ck-us.net>,
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 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.
> > 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].
Adrian
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/glaubitz/sh-linux.git/log/?h=for-next
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists