From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>, <suraj.kandpal@intel.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 0/2] Fixes in snps-phy HDMI PLL algorithm
Date: Thu, 19 Jun 2025 17:26:46 +0530 [thread overview]
Message-ID: <e2d8f3bd-112d-4e5a-9e6e-9a394b62d797@intel.com> (raw)
In-Reply-To: <2e0169d6e2d533e4b0175937961d91ae8da4799e@intel.com>
On 6/19/2025 1:21 AM, Jani Nikula wrote:
> 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>
Thank you once again, Jani, for pointing out the sparse warning and for
your reviews.
The series has been pushed to drm-intel-next.
Regards,
Ankit
>
>> 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(-)
next prev parent reply other threads:[~2025-06-19 11:57 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 ` [PATCH 0/2] " Jani Nikula
2025-06-19 11:56 ` Nautiyal, Ankit K [this message]
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=e2d8f3bd-112d-4e5a-9e6e-9a394b62d797@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--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