Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] clk: qcom: camcc-sc8280xp: Remove always-on GDSC hard-coding
Date: Mon, 15 Jul 2024 23:09:39 +0800	[thread overview]
Message-ID: <ZpU7s85rGn6CGCa1@6724a33121ae> (raw)
In-Reply-To: <20240715-linux-next-24-07-13-sc8280xp-camcc-fixes-v1-1-fadb5d9445c1@linaro.org>

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] clk: qcom: camcc-sc8280xp: Remove always-on GDSC hard-coding
Link: https://lore.kernel.org/stable/20240715-linux-next-24-07-13-sc8280xp-camcc-fixes-v1-1-fadb5d9445c1%40linaro.org

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




  reply	other threads:[~2024-07-15 15:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 14:59 [PATCH] clk: qcom: camcc-sc8280xp: Remove always-on GDSC hard-coding Bryan O'Donoghue
2024-07-15 15:09 ` kernel test robot [this message]
2024-07-17  6:32 ` Satya Priya Kakitapalli (Temp)
2024-07-17  8:49   ` Bryan O'Donoghue
2024-07-17 11:08     ` Satya Priya Kakitapalli (Temp)
2024-07-17 11:11       ` Bryan O'Donoghue
2024-07-19  7:25         ` Satya Priya Kakitapalli (Temp)
2024-07-20  8:33           ` Bryan O'Donoghue
2024-07-22  8:57             ` Satya Priya Kakitapalli (Temp)
2024-07-23  9:29               ` Bryan O'Donoghue
2024-07-23 11:37                 ` Satya Priya Kakitapalli (Temp)
2024-07-23 11:49                   ` Dmitry Baryshkov
2024-07-26  7:01                 ` Satya Priya Kakitapalli (Temp)
2024-07-26 20:31                   ` Bryan O'Donoghue
2024-07-29 10:57                     ` Satya Priya Kakitapalli (Temp)

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=ZpU7s85rGn6CGCa1@6724a33121ae \
    --to=lkp@intel.com \
    --cc=bryan.odonoghue@linaro.org \
    --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