From: kernel test robot <lkp@intel.com>
To: Yang Xiwen via B4 Relay <devnull+forbidden405.outlook.com@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 2/3] arm64: dts: hi3798cv200: add GICH, GICV register space and irq
Date: Mon, 19 Feb 2024 23:11:37 +0800 [thread overview]
Message-ID: <ZdNvqZiRZLYMuHqe@c528657181df> (raw)
In-Reply-To: <20240219-cache-v3-2-a33c57534ae9@outlook.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 2/3] arm64: dts: hi3798cv200: add GICH, GICV register space and irq
Link: https://lore.kernel.org/stable/20240219-cache-v3-2-a33c57534ae9%40outlook.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-19 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 15:05 [PATCH v3 0/3] arm64: dts: hi3798cv200: fix GICR size, add cache info, maintenance irq and GICH, GICV spaces Yang Xiwen via B4 Relay
2024-02-19 15:05 ` [PATCH v3 1/3] arm64: dts: hi3798cv200: fix the size of GICR Yang Xiwen via B4 Relay
2024-02-19 15:05 ` [PATCH v3 2/3] arm64: dts: hi3798cv200: add GICH, GICV register space and irq Yang Xiwen via B4 Relay
2024-02-19 15:11 ` kernel test robot [this message]
2024-02-19 15:05 ` [PATCH v3 3/3] arm64: dts: hi3798cv200: add cache info Yang Xiwen via B4 Relay
2024-03-12 11:19 ` [PATCH v3 0/3] arm64: dts: hi3798cv200: fix GICR size, add cache info, maintenance irq and GICH, GICV spaces Yang Xiwen
2024-03-12 11:33 ` Wei Xu
2024-03-12 11:46 ` Yang Xiwen
2024-03-12 11:58 ` Wei Xu
2024-03-12 11:36 ` Krzysztof Kozlowski
2024-03-12 12:00 ` Wei Xu
2024-04-08 7:31 ` Krzysztof Kozlowski
2024-04-08 8:09 ` Wei Xu
2024-04-08 9:09 ` Yang Xiwen
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=ZdNvqZiRZLYMuHqe@c528657181df \
--to=lkp@intel.com \
--cc=devnull+forbidden405.outlook.com@kernel.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