From: Nick Hastings <nicholaschastings@gmail.com>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
Lukas Wunner <lukas@wunner.de>,
Salvatore Bonaccorso <carnil@debian.org>,
"1036530@bugs.debian.org" <1036530@bugs.debian.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)
Date: Sat, 1 Jul 2023 07:12:56 +0900 [thread overview]
Message-ID: <ZJ9TaCiYMiRAXm81@xps> (raw)
In-Reply-To: <0bdbb7a3-b8fa-1afa-23cf-afde1cec3d25@amd.com>
Hi,
* Limonciello, Mario <mario.limonciello@amd.com> [230701 06:40]:
>
> > > Nevertheless: thx for your report your help through this thread.
> >
> > No problem. I am willing to try to do more, but right now I don't know
> > how to do what has been suggested.
> >
>
> Here is where to report Nouveau bugs:
>
> https://gitlab.freedesktop.org/drm/nouveau/-/issues/
Thanks.
Done: https://gitlab.freedesktop.org/drm/nouveau/-/issues/241
Cheers,
Nick.
next prev parent reply other threads:[~2023-06-30 22:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZG3mbc3zdR4KcUW/@eldamar.lan>
[not found] ` <ZG6cY8xjfob4Bvcs@xps>
[not found] ` <ZG98fQ+MD4O0nGGE@eldamar.lan>
[not found] ` <ZG/8cxxTJ9ZzrVPQ@xps>
[not found] ` <ZHCYRmD7YeIWoy2W@eldamar.lan>
[not found] ` <168471337231.1913606.15905047692536779158.reportbug@xps>
[not found] ` <ZHKrC4/G6ZyvRReI@xps>
2023-05-28 6:49 ` Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system) Salvatore Bonaccorso
2023-05-28 12:44 ` Mario Limonciello
[not found] ` <ZHP4IqxBUPuVRvRV@xps>
2023-05-29 1:14 ` Mario Limonciello
2023-05-29 3:51 ` Nick Hastings
2023-05-29 23:01 ` Nick Hastings
2023-05-30 4:00 ` Mario Limonciello
2023-05-30 7:01 ` Nick Hastings
2023-05-30 11:22 ` Bug#1036530: " Salvatore Bonaccorso
2023-05-31 23:40 ` Nick Hastings
2023-06-01 16:18 ` Limonciello, Mario
2023-06-01 16:33 ` Karol Herbst
2023-06-01 16:54 ` Limonciello, Mario
2023-06-01 17:18 ` Karol Herbst
2023-06-01 17:21 ` Limonciello, Mario
2023-06-01 18:10 ` Karol Herbst
2023-06-02 0:01 ` Nick Hastings
2023-06-02 0:57 ` Limonciello, Mario
2023-06-26 12:09 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-26 22:34 ` Nick Hastings
2023-06-30 13:02 ` Thorsten Leemhuis
2023-06-30 13:09 ` Karol Herbst
2023-06-30 21:38 ` Nick Hastings
2023-06-30 21:40 ` Limonciello, Mario
2023-06-30 22:12 ` Nick Hastings [this message]
2023-06-01 23:55 ` Nick Hastings
2023-07-07 21:54 ` Lyude Paul
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=ZJ9TaCiYMiRAXm81@xps \
--to=nicholaschastings@gmail.com \
--cc=1036530@bugs.debian.org \
--cc=carnil@debian.org \
--cc=kherbst@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=lyude@redhat.com \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox