[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4a51dc10-786e-e07c-4b2a-fc63e63d99d6@physik.fu-berlin.de>
Date: Fri, 8 Oct 2021 20:29:08 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Rich Felker <dalias@...c.org>
Cc: Daniel Palmer <daniel@...f.com>,
Randy Dunlap <rdunlap@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Linux-sh list <linux-sh@...r.kernel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>, j-core@...ore.org
Subject: Re: [PATCH 0/3 v2] sh: fixes for various build and kconfig warnings
Hi Rich!
On 9/22/21 04:45, Rich Felker wrote:
> I didn't get through that yet, but I have rebased the patches that
> were pending in for-next onto v5.15-rc1 (no conflicts) and
> smoke-tested that a sh4 build runs in my qemu environment. linux-next
> pulled them 27 hours ago and hasn't complained yet either.
Do we need another PR against Linus' tree from your side or are they pulled
in automatically?
> I started going through the list/patch backlog, but didn't make it
> nearly as far as I'd like yet. If you have even a vague list of what's
> important (warnings breaking the build, unapplied changes blocking
> removal of cruft from other parts of the kernel and making people
> unhappy with us, etc.) that would be really helpful.
>
> I'll follow up again soon.
Any news on this?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@...ian.org
`. `' Freie Universitaet Berlin - glaubitz@...sik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists