From: Francesco Magazzu <postadelmaga@gmail.com>
To: lyude@redhat.com, dakr@kernel.org
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org, kherbst@redhat.com
Subject: Re: [PATCH 0/2] drm/nouveau/clk: fix RAM error handling and pstate desync in nvkm_pstate_prog
Date: Sat, 1 Aug 2026 14:11:22 +0200 [thread overview]
Message-ID: <20260801121122.358187-1-postadelmaga@gmail.com> (raw)
In-Reply-To: <20260727152821.128432-1-postadelmaga@gmail.com>
Note: this series applies on top of my earlier "[PATCH v2 0/4]
drm/nouveau: fix list cursor use after loop in the clk pstate paths"
(20260712123616.1180830-1-postadelmaga@gmail.com, sent 2026-07-12), not
on a clean tree -- patch 2/2 here touches the same nvkm_pstate_prog()
that v2's patch 2/4 modifies.
Both patches fix pre-existing issues an automated review (Sashiko)
found in v2's patch 2/4 while reviewing it: nvkm_pstate_prog() silently
discarding RAM clock programming errors, and clk->pstate being updated
before hardware programming actually succeeds. Neither bug was
introduced by v2 itself.
If it's easier to review as one unit, happy to resend as a v3 of the
original series with these two folded in -- let me know what you'd
prefer.
Francesco
prev parent reply other threads:[~2026-08-01 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 15:28 Francesco Magazzu
2026-07-27 15:28 ` [PATCH 1/2] drm/nouveau/clk: don't ignore RAM clock programming errors " Francesco Magazzu
2026-07-27 15:28 ` [PATCH 2/2] drm/nouveau/clk: only update clk->pstate after hardware programming succeeds Francesco Magazzu
2026-08-01 12:11 ` Francesco Magazzu [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=20260801121122.358187-1-postadelmaga@gmail.com \
--to=postadelmaga@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
/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
all inboxes | Powered by JetHome®