[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWqXHajFnBq8gaPbZqRSdZ7kvOCBsKzxEN9ncCvwjcBqg@mail.gmail.com>
Date: Tue, 20 Feb 2024 21:51:55 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Guenter Roeck <linux@...ck-us.net>, Matthew Auld <matthew.auld@...el.com>,
Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@....com>,
Christian König <christian.koenig@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 6.8-rc5
Hi Linus,
On Tue, Feb 20, 2024 at 8:58 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Tue, 20 Feb 2024 at 11:09, Guenter Roeck <linux@...ck-us.net> wrote:
> > Build results:
> > total: 155 pass: 151 fail: 4
> > Failed builds:
> > csky:allmodconfig
> > openrisc:allmodconfig
> > parisc:allmodconfig
> > xtensa:allmodconfig
> > Qemu test results:
> > total: 549 pass: 547 fail: 2
>
> Grr, I was hoping things would improve, not go backwards.
>
> > ERROR: modpost: "__umoddi3" [drivers/gpu/drm/tests/drm_buddy_test.ko] undefined!
> > ERROR: modpost: "__moddi3" [drivers/gpu/drm/tests/drm_buddy_test.ko] undefined!
> >
> > Commit a64056bb5a32 ("drm/tests/drm_buddy: add alloc_contiguous test"):
[...]
> Suggested untested patch attached.
Thanks, your patch is already the third fix I am aware of.
That is one of the issues with build problems like this: once it is
upstream, too many people become affected, and write a patch.
And all of that could have been avoided if the buggy commit was not
included in a PR _after_ the breakage was reported...
Now back to bisecting other runtime breakage in next...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68korg
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
Powered by blists - more mailing lists