public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jiasheng Jiang <jiashengjiangcool@gmail.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 net-next] dpll: Add an assertion to check freq_supported_num
Date: Thu, 27 Feb 2025 03:38:33 +0800	[thread overview]
Message-ID: <Z79tucNAlwpGo_1Z@c9d8a7425515> (raw)
In-Reply-To: <20250226193715.23898-1-jiashengjiangcool@gmail.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 v3 net-next] dpll: Add an assertion to check freq_supported_num
Link: https://lore.kernel.org/stable/20250226193715.23898-1-jiashengjiangcool%40gmail.com

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




  reply	other threads:[~2025-02-26 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23 20:17 [PATCH] dpll: Add a check before kfree() to match the existing check before kmemdup() Jiasheng Jiang
2025-02-24  9:31 ` Kubalewski, Arkadiusz
2025-02-24 12:04   ` Jiri Pirko
2025-02-24 16:47     ` Jiasheng Jiang
2025-02-25 12:08       ` Jiri Pirko
2025-02-26  3:09         ` [PATCH v2] dpll: Add an assertion to check freq_supported_num Jiasheng Jiang
2025-02-26 14:24           ` Jiri Pirko
2025-02-26 19:37             ` [PATCH v3 net-next] " Jiasheng Jiang
2025-02-26 19:38               ` kernel test robot [this message]
2025-02-27  5:21               ` Przemek Kitszel

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=Z79tucNAlwpGo_1Z@c9d8a7425515 \
    --to=lkp@intel.com \
    --cc=jiashengjiangcool@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox