From: "Linux kernel regression tracking (#update)" <regressions@leemhuis.info>
To: bskeggs@redhat.com, Karol Herbst <kherbst@redhat.com>,
Lyude Paul <lyude@redhat.com>
Cc: regressions@lists.linux.dev, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org, airlied@redhat.com,
Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Subject: Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Fri, 3 Feb 2023 10:13:34 +0100 [thread overview]
Message-ID: <2445e228-37d0-ef64-7abf-bfa14e10f9cc@leemhuis.info> (raw)
In-Reply-To: <c32ea02c-d706-ea2f-aa13-660b8db958ef@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
#regzbot fix: drm/nouveau/acr/gm20b: regression fixes
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
WARNING: multiple messages have this Message-ID (diff)
From: "Linux kernel regression tracking (#update)" <regressions@leemhuis.info>
To: bskeggs@redhat.com, Karol Herbst <kherbst@redhat.com>,
Lyude Paul <lyude@redhat.com>
Cc: nouveau@lists.freedesktop.org,
Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
regressions@lists.linux.dev, dri-devel@lists.freedesktop.org,
airlied@redhat.com
Subject: Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Fri, 3 Feb 2023 10:13:34 +0100 [thread overview]
Message-ID: <2445e228-37d0-ef64-7abf-bfa14e10f9cc@leemhuis.info> (raw)
In-Reply-To: <c32ea02c-d706-ea2f-aa13-660b8db958ef@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
#regzbot fix: drm/nouveau/acr/gm20b: regression fixes
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
WARNING: multiple messages have this Message-ID (diff)
From: "Linux kernel regression tracking (#update)" <regressions@leemhuis.info>
To: bskeggs@redhat.com, Karol Herbst <kherbst@redhat.com>,
Lyude Paul <lyude@redhat.com>
Cc: nouveau@lists.freedesktop.org,
Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
regressions@lists.linux.dev, dri-devel@lists.freedesktop.org,
airlied@redhat.com
Subject: Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Fri, 3 Feb 2023 10:13:34 +0100 [thread overview]
Message-ID: <2445e228-37d0-ef64-7abf-bfa14e10f9cc@leemhuis.info> (raw)
In-Reply-To: <c32ea02c-d706-ea2f-aa13-660b8db958ef@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report was posted more
> than a week ago and didn't even get a single reply yet afaics. This of
> course can happen at this time of the year, but I nevertheless thought a
> quick status inquiry might be a good idea at this point.
#regzbot fix: drm/nouveau/acr/gm20b: regression fixes
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-02-03 9:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 14:49 [REGRESSION] GM20B probe fails after commit 2541626cfb79 Diogo Ivo
2022-12-28 14:49 ` [Nouveau] " Diogo Ivo
2022-12-28 14:49 ` Diogo Ivo
2023-01-05 12:28 ` Thorsten Leemhuis
2023-01-05 12:28 ` [Nouveau] " Thorsten Leemhuis
2023-01-05 12:28 ` Thorsten Leemhuis
2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 13:19 ` [Nouveau] " Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-14 3:27 ` Karol Herbst
2023-01-14 3:27 ` Karol Herbst
2023-01-14 3:27 ` Karol Herbst
2023-01-14 16:03 ` Diogo Ivo
2023-01-14 16:03 ` [Nouveau] " Diogo Ivo
2023-01-14 16:03 ` Diogo Ivo
2023-01-14 18:56 ` Karol Herbst
2023-01-14 18:56 ` Karol Herbst
2023-01-14 18:56 ` [Nouveau] " Karol Herbst
2023-01-14 15:58 ` Diogo Ivo
2023-01-14 15:58 ` [Nouveau] " Diogo Ivo
2023-01-14 15:58 ` Diogo Ivo
2023-02-03 9:13 ` Linux kernel regression tracking (#update) [this message]
2023-02-03 9:13 ` Linux kernel regression tracking (#update)
2023-02-03 9:13 ` [Nouveau] " Linux kernel regression tracking (#update)
2023-01-15 21:45 ` David Airlie
2023-01-15 21:45 ` David Airlie
2023-01-15 21:45 ` [Nouveau] " David Airlie
2023-01-16 12:24 ` Diogo Ivo
2023-01-16 12:24 ` [Nouveau] " Diogo Ivo
2023-01-16 12:24 ` Diogo Ivo
2023-01-18 1:28 ` [Nouveau] " Ben Skeggs
2023-01-18 1:28 ` Ben Skeggs
2023-01-18 1:28 ` Ben Skeggs
2023-01-18 8:42 ` [Nouveau] " Nicolas Chauvet
2023-01-18 8:42 ` Nicolas Chauvet
2023-01-20 11:34 ` Diogo Ivo
2023-01-20 11:34 ` [Nouveau] " Diogo Ivo
2023-01-20 11:34 ` Diogo Ivo
2023-01-27 6:00 ` Ben Skeggs
2023-01-27 6:00 ` Ben Skeggs
2023-01-27 6:00 ` [Nouveau] " Ben Skeggs
2023-01-27 9:03 ` Nicolas Chauvet
2023-01-27 9:03 ` Nicolas Chauvet
2023-01-27 9:03 ` [Nouveau] " Nicolas Chauvet
2023-01-27 10:48 ` Diogo Ivo
2023-01-27 10:48 ` [Nouveau] " Diogo Ivo
2023-01-27 10:39 ` Diogo Ivo
2023-01-27 10:39 ` [Nouveau] " Diogo Ivo
2023-01-27 10:39 ` Diogo Ivo
2023-01-29 22:36 ` Ben Skeggs
2023-01-29 22:36 ` Ben Skeggs
2023-01-29 22:36 ` [Nouveau] " Ben Skeggs
2023-01-30 13:54 ` Diogo Ivo
2023-01-30 13:54 ` [Nouveau] " Diogo Ivo
2023-01-30 13:54 ` Diogo Ivo
2023-01-30 16:05 ` Nicolas Chauvet
2023-01-30 16:05 ` Nicolas Chauvet
2023-01-30 16:05 ` [Nouveau] " Nicolas Chauvet
2023-01-17 15:55 ` Nicolas Chauvet
2023-01-17 15:55 ` Nicolas Chauvet
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=2445e228-37d0-ef64-7abf-bfa14e10f9cc@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.