From: "Danilo Krummrich" <dakr@kernel.org>
To: <maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: (subset) [PATCH v2 00/10] drm/nouveau: fix GA100 issues
Date: Wed, 20 May 2026 23:07:05 +0200 [thread overview]
Message-ID: <DINT6SMFR28W.3P32OZYOA5GRU@kernel.org> (raw)
In-Reply-To: <0079fcd18a9840c45f751d86dfb870cd1f36655e.camel@nvidia.com>
Hi Maarten, Maxime, Thomas,
On Tue May 19, 2026 at 3:36 PM CEST, Timur Tabi wrote:
> On Fri, 2026-05-01 at 01:10 +0200, Danilo Krummrich wrote:
>> On Thu, 30 Apr 2026 17:38:28 -0500, Timur Tabi wrote:
>> > [PATCH v2 00/10] drm/nouveau: fix GA100 issues
>>
>> Applied, thanks!
>>
>> Branch: drm-misc-fixes
>> Tree: https://gitlab.freedesktop.org/drm/misc/kernel.git
>>
>> [1/10] Revert "drm/nouveau/gsp: add support for GA100"
>> commit: c9e3878ae2f5
>>
>> The patch will appear in the next linux-next integration (typically within 24
>> hours on weekdays).
>>
>> The patch is queued up for Linus's tree and should land in the next -rc release.
>
> Danilo,
>
> What's the plan for the rest of the patch set?
Can we please get drm-fixes-2026-05-08-1 (commit c9e3878ae2f5 ("Revert
"drm/nouveau/gsp: add support for GA100"") backmerged into drm-misc-next?
Thanks,
Danilo
next prev parent reply other threads:[~2026-05-20 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 22:38 [PATCH v2 00/10] drm/nouveau: fix GA100 issues Timur Tabi
2026-04-30 22:38 ` [PATCH v2 01/10] Revert "drm/nouveau/gsp: add support for GA100" Timur Tabi
2026-04-30 22:38 ` [PATCH v2 02/10] drm/nouveau/gsp: add SEC2 to GA100 chip table Timur Tabi
2026-04-30 22:38 ` [PATCH v2 03/10] drm/nouveau/gsp: use fb.bios.addr for gspFwWprEnd instead of vga_workspace.addr Timur Tabi
2026-04-30 22:38 ` [PATCH v2 04/10] drm/nouveau/gsp: read MMU_LOCK to fix WPR placement on GA100 Timur Tabi
2026-04-30 22:38 ` [PATCH v2 05/10] drm/nouveau: only boot FRTS if its region is allocated Timur Tabi
2026-04-30 22:38 ` [PATCH v2 06/10] drm/nouveau: GA100 has an FRTS region size of zero Timur Tabi
2026-04-30 22:38 ` [PATCH v2 07/10] drm/nouveau/bios: specify correct display fuse register for Ampere and Ada Timur Tabi
2026-04-30 22:38 ` [PATCH v2 08/10] drm/nouveau/bios: skip the IFR header if present Timur Tabi
2026-04-30 22:38 ` [PATCH v2 09/10] drm/nouveau/gsp: require GSP-RM for GA100 support Timur Tabi
2026-04-30 22:38 ` [PATCH v2 10/10] drm/nouveau/gsp: formally support GA100 Timur Tabi
2026-04-30 23:10 ` (subset) [PATCH v2 00/10] drm/nouveau: fix GA100 issues Danilo Krummrich
2026-05-19 13:36 ` Timur Tabi
2026-05-20 21:07 ` Danilo Krummrich [this message]
2026-05-28 17:33 ` Danilo Krummrich
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=DINT6SMFR28W.3P32OZYOA5GRU@kernel.org \
--to=dakr@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--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 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.