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 1/2] drm/i915/display: Add macro for checking 3 DSC engines
Date: Mon, 14 Apr 2025 11:27:26 +0800 [thread overview]
Message-ID: <Z_yAnpQDMXmCRYSO@6bf5cb62fcc2> (raw)
In-Reply-To: <20250414024256.2782702-2-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 1/2] drm/i915/display: Add macro for checking 3 DSC engines
Link: https://lore.kernel.org/stable/20250414024256.2782702-2-ankit.k.nautiyal%40intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-14 3:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 2:42 [PATCH 0/2] Macro for 3 DSC engines per pipe Ankit Nautiyal
2025-04-14 2:42 ` [PATCH 1/2] drm/i915/display: Add macro for checking 3 DSC engines Ankit Nautiyal
2025-04-14 3:27 ` kernel test robot [this message]
2025-04-14 3:48 ` Kandpal, Suraj
2025-04-14 4:05 ` Nautiyal, Ankit K
2025-04-14 4:06 ` Kandpal, Suraj
2025-04-14 8:57 ` Ankit Nautiyal
2025-04-14 9:12 ` Kandpal, Suraj
2025-04-15 7:17 ` Jani Nikula
2025-04-15 7:43 ` Nautiyal, Ankit K
2025-04-14 2:42 ` [PATCH 2/2] drm/i915/dp: Check for HAS_DSC_3ENGINES while configuring DSC slices Ankit Nautiyal
2025-04-14 4:07 ` Kandpal, Suraj
2025-04-14 3:10 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines Patchwork
2025-04-14 3:11 ` ✓ CI.checkpatch: " Patchwork
2025-04-14 3:12 ` ✓ CI.KUnit: " Patchwork
2025-04-14 3:20 ` ✓ CI.Build: " Patchwork
2025-04-14 3:23 ` ✓ CI.Hooks: " Patchwork
2025-04-14 3:24 ` ✗ CI.checksparse: warning " Patchwork
2025-04-14 3:56 ` ✗ Fi.CI.SPARSE: warning for Macro for 3 DSC engines per pipe Patchwork
2025-04-14 4:09 ` ✓ Xe.CI.BAT: success for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines Patchwork
2025-04-14 5:23 ` ✓ i915.CI.BAT: success for Macro for 3 DSC engines per pipe Patchwork
2025-04-14 5:34 ` ✗ Xe.CI.Full: failure for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines Patchwork
2025-04-14 9:17 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines (rev2) Patchwork
2025-04-14 9:22 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-14 9:29 ` ✓ CI.KUnit: success " Patchwork
2025-04-14 9:34 ` ✓ CI.Build: " Patchwork
2025-04-14 9:36 ` ✓ CI.Hooks: " Patchwork
2025-04-14 9:37 ` ✗ CI.checksparse: warning " Patchwork
2025-04-14 10:19 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-14 10:24 ` ✗ Fi.CI.CHECKPATCH: warning for Macro for 3 DSC engines per pipe (rev2) Patchwork
2025-04-14 10:24 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-14 10:46 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-14 11:50 ` ✗ Xe.CI.Full: failure for series starting with [1/2] drm/i915/display: Add macro for checking 3 DSC engines (rev2) Patchwork
2025-04-14 13:16 ` ✗ i915.CI.Full: failure for Macro for 3 DSC engines per pipe (rev2) Patchwork
2025-04-15 4:42 ` ✓ 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=Z_yAnpQDMXmCRYSO@6bf5cb62fcc2 \
--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.