From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Helge Deller <deller@gmx.de>,
Javier Martinez Canillas <javierm@redhat.com>,
linux-fbdev@vger.kernel.org,
Linux PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Regressions <regressions@lists.linux.dev>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 13 (drivers/video/fbdev/ps3fb.c)
Date: Wed, 19 Jul 2023 19:36:46 +0700 [thread overview]
Message-ID: <5983cf9d-dc1e-75bd-3624-770951661245@gmail.com> (raw)
In-Reply-To: <f5e6258b-ba76-001b-4942-588f4cbb0aa7@leemhuis.info>
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
next prev parent reply other threads:[~2023-07-19 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 2:37 linux-next: Tree for Jul 13 Stephen Rothwell
2023-07-13 16:11 ` linux-next: Tree for Jul 13 (drivers/video/fbdev/ps3fb.c) Randy Dunlap
2023-07-14 20:46 ` Randy Dunlap
2023-07-18 3:32 ` Bagas Sanjaya
2023-07-18 10:06 ` Thorsten Leemhuis
2023-07-19 12:36 ` Bagas Sanjaya [this message]
2023-07-19 12:48 ` Thorsten Leemhuis
2023-07-18 11:48 ` Michael Ellerman
2023-07-18 12:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-18 16:15 ` Randy Dunlap
2023-07-31 11:53 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-31 12:33 ` Helge Deller
2023-07-31 14:01 ` Thomas Zimmermann
2023-07-18 0:45 Randy Dunlap
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=5983cf9d-dc1e-75bd-3624-770951661245@gmail.com \
--to=bagasdotme@gmail.com \
--cc=deller@gmx.de \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rdunlap@infradead.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).