Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Timur Tabi <ttabi@nvidia.com>
Cc: Danilo Krummrich <dakr@kernel.org>, nouveau@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/nouveau: expose VBIOS via debugfs on GSP-RM systems
Date: Wed, 29 Apr 2026 23:57:34 +0200	[thread overview]
Message-ID: <20260429215734.5282-1-dakr@kernel.org> (raw)
In-Reply-To: <20260428202825.1123719-1-ttabi@nvidia.com>

On Tue, 28 Apr 2026 15:28:25 -0500, Timur Tabi wrote:
> [PATCH v2] drm/nouveau: expose VBIOS via debugfs on GSP-RM systems

Applied, thanks!

  Branch: drm-misc-next
  Tree:   https://gitlab.freedesktop.org/drm/misc/kernel.git

[1/1] drm/nouveau: expose VBIOS via debugfs on GSP-RM systems
      commit: a5640267d6d3

The patch will appear in the next linux-next integration (typically within 24
hours on weekdays).

The patch is queued up for the upcoming merge window for the next major kernel
release.

      reply	other threads:[~2026-04-29 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 20:28 [PATCH v2] drm/nouveau: expose VBIOS via debugfs on GSP-RM systems Timur Tabi
2026-04-29 21:57 ` Danilo Krummrich [this message]

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=20260429215734.5282-1-dakr@kernel.org \
    --to=dakr@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ttabi@nvidia.com \
    /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