public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/7] arm64: dts: imx8mm-venice-gw7901: Increase HS400 USDHC clock speed
Date: Tue, 8 Jul 2025 04:54:31 +0800	[thread overview]
Message-ID: <aGw0BwGfTEDO8kOG@319465d791e2> (raw)
In-Reply-To: <20250707201702.2930066-3-tharvey@gateworks.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 3/7] arm64: dts: imx8mm-venice-gw7901: Increase HS400 USDHC clock speed
Link: https://lore.kernel.org/stable/20250707201702.2930066-3-tharvey%40gateworks.com

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




  reply	other threads:[~2025-07-07 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 20:16 [PATCH 1/7] arm64: dts: imx8mm-venice-gw700x: Increase HS400 USDHC clock speed Tim Harvey
2025-07-07 20:16 ` [PATCH 2/7] arm64: dts: imx8mp-venice-gw702x: " Tim Harvey
2025-07-07 20:16 ` [PATCH 3/7] arm64: dts: imx8mm-venice-gw7901: " Tim Harvey
2025-07-07 20:54   ` kernel test robot [this message]
2025-07-07 20:16 ` [PATCH 4/7] arm64: dts: imx8mm-venice-gw7902: " Tim Harvey
2025-07-07 20:17 ` [PATCH 5/7] arm64: dts: imx8mn-venice-gw7902: " Tim Harvey
2025-07-07 20:17 ` [PATCH 6/7] arm64: dts: imx8mm-venice-gw7903: " Tim Harvey
2025-07-07 20:17 ` [PATCH 7/7] arm64: dts: imx8mm-venice-gw7904: " Tim Harvey
2025-07-11  8:04 ` [PATCH 1/7] arm64: dts: imx8mm-venice-gw700x: " Shawn Guo

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=aGw0BwGfTEDO8kOG@319465d791e2 \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tharvey@gateworks.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