Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, suraj.kandpal@intel.com,
	stable@vger.kernel.org,
	Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH 0/2] Fixes in snps-phy HDMI PLL algorithm
Date: Wed, 18 Jun 2025 22:51:15 +0300	[thread overview]
Message-ID: <2e0169d6e2d533e4b0175937961d91ae8da4799e@intel.com> (raw)
In-Reply-To: <20250618130951.1596587-1-ankit.k.nautiyal@intel.com>

On Wed, 18 Jun 2025, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Fixes/improvement in snps-phy HDMI PLL algorithm.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

>
> Ankit Nautiyal (2):
>   drm/i915/snps_hdmi_pll: Fix 64-bit divisor truncation by using
>     div64_u64
>   drm/i915/snps_hdmi_pll: Use clamp() instead of max(min())
>
>  drivers/gpu/drm/i915/display/intel_snps_hdmi_pll.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-06-18 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 13:09 [PATCH 0/2] Fixes in snps-phy HDMI PLL algorithm Ankit Nautiyal
2025-06-18 13:09 ` [PATCH 1/2] drm/i915/snps_hdmi_pll: Fix 64-bit divisor truncation by using div64_u64 Ankit Nautiyal
2025-06-18 13:09 ` [PATCH 2/2] drm/i915/snps_hdmi_pll: Use clamp() instead of max(min()) Ankit Nautiyal
2025-06-18 14:36 ` ✓ i915.CI.BAT: success for Fixes in snps-phy HDMI PLL algorithm Patchwork
2025-06-18 19:51 ` Jani Nikula [this message]
2025-06-19 11:56   ` [PATCH 0/2] " Nautiyal, Ankit K
2025-06-19  5:44 ` ✗ i915.CI.Full: failure for " Patchwork
2025-06-19  9:23 ` ✓ i915.CI.Full: success " Patchwork

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=2e0169d6e2d533e4b0175937961d91ae8da4799e@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --cc=suraj.kandpal@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