[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5983cf9d-dc1e-75bd-3624-770951661245@gmail.com>
Date: Wed, 19 Jul 2023 19:36:46 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Thorsten Leemhuis <regressions@...mhuis.info>,
Randy Dunlap <rdunlap@...radead.org>,
Thomas Zimmermann <tzimmermann@...e.de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Helge Deller <deller@....de>,
Javier Martinez Canillas <javierm@...hat.com>,
linux-fbdev@...r.kernel.org,
Linux PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Tree for Jul 13 (drivers/video/fbdev/ps3fb.c)
On 7/18/23 17:06, Thorsten Leemhuis wrote:
> I'm missing something here:
>
> * What makes you think this is caused by bdb616479eff419? I didn't see
> anything in the thread that claims this, but I might be missing something
> * related: if I understand Randy right, this is only happening in -next;
> so why is bdb616479eff419 the culprit, which is also in mainline since
> End of June?
>
Actually drivers/video/fbdev/ps3bf.c only had two non-merge commits during
previous cycle: 25ec15abb06194 and bdb616479eff419. The former was simply
adding .owner field in ps3fb_ops (hence trivial), so I inferred that the
culprit was likely the latter (due to it was being authored by Thomas).
Thanks for the question.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists