Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, tools@kernel.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 01/14] drm/i915/cdclk: Don't bail if pcode post nofify fails
Date: Wed, 17 Jun 2026 16:29:16 +0300	[thread overview]
Message-ID: <8c18eca330bd63182319a18f238e78f1c451ede2@intel.com> (raw)
In-Reply-To: <511da82834da302ac50a326c082c45f6134b2556@intel.com>

On Wed, 10 Jun 2026, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 10 Jun 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>
>> We already changed the actual cdclk frequency by the time we do
>> the pcode post notify. So skipping the subsequent readout is plain
>> wrong.
>
> Fixes: ?

Turns out posing the question about Fixes: trailer like that leads to b4
shazam literally adding that trailer. Please clean them up before
pushing!

Cc: tools@k.o and Konstantin, FYI


BR,
Jani.


-- 
Jani Nikula, Intel

       reply	other threads:[~2026-06-17 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260610170652.5320-1-ville.syrjala@linux.intel.com>
     [not found] ` <20260610170652.5320-2-ville.syrjala@linux.intel.com>
     [not found]   ` <511da82834da302ac50a326c082c45f6134b2556@intel.com>
2026-06-17 13:29     ` Jani Nikula [this message]
2026-06-17 15:15       ` [PATCH 01/14] drm/i915/cdclk: Don't bail if pcode post nofify fails Konstantin Ryabitsev

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=8c18eca330bd63182319a18f238e78f1c451ede2@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@kernel.org \
    --cc=ville.syrjala@linux.intel.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