All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/2] drm/i915/snps_hdmi_pll: Use clamp() instead of max(min())
Date: Wed, 18 Jun 2025 21:21:27 +0800	[thread overview]
Message-ID: <aFK9V7_jQE9aExj9@d8702eadd420> (raw)
In-Reply-To: <20250618130951.1596587-3-ankit.k.nautiyal@intel.com>

Hi,

Thanks for your patch.

FYI: kernel test robot notices the stable kernel rule is not satisfied.

The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-1

Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree.
Subject: [PATCH 2/2] drm/i915/snps_hdmi_pll: Use clamp() instead of max(min())
Link: https://lore.kernel.org/stable/20250618130951.1596587-3-ankit.k.nautiyal%40intel.com

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki




  reply	other threads:[~2025-06-18 13:21 UTC|newest]

Thread overview: 13+ 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 13:21   ` kernel test robot [this message]
2025-06-18 13:27 ` ✓ CI.KUnit: success for Fixes in snps-phy HDMI PLL algorithm Patchwork
2025-06-18 13:41 ` ✗ CI.checksparse: warning " Patchwork
2025-06-18 14:17 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-18 14:36 ` ✓ i915.CI.BAT: " Patchwork
2025-06-18 19:51 ` [PATCH 0/2] " Jani Nikula
2025-06-19 11:56   ` Nautiyal, Ankit K
2025-06-19  4:09 ` ✓ Xe.CI.Full: success for " Patchwork
2025-06-19  5:44 ` ✗ i915.CI.Full: failure " 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=aFK9V7_jQE9aExj9@d8702eadd420 \
    --to=lkp@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.