From: kernel test robot <lkp@intel.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 3/4] arm64: dts: ti: k3-j722s-main: don't disable serdes0 and serdes1
Date: Thu, 17 Apr 2025 20:34:17 +0800 [thread overview]
Message-ID: <aAD1SRN8CkYEvIof@4cfa58227a13> (raw)
In-Reply-To: <20250417123246.2733923-4-s-vadapalli@ti.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 3/4] arm64: dts: ti: k3-j722s-main: don't disable serdes0 and serdes1
Link: https://lore.kernel.org/stable/20250417123246.2733923-4-s-vadapalli%40ti.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-17 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 12:32 [PATCH v3 0/4] J722S: Disable WIZ0 and WIZ1 in SoC file Siddharth Vadapalli
2025-04-17 12:32 ` [PATCH v3 1/4] arm64: dts: ti: k3-j722s-evm: Enable "serdes_wiz0" and "serdes_wiz1" Siddharth Vadapalli
2025-04-17 12:32 ` [PATCH v3 2/4] arm64: dts: ti: k3-j722s-main: Disable " Siddharth Vadapalli
2025-04-17 12:32 ` [PATCH v3 3/4] arm64: dts: ti: k3-j722s-main: don't disable serdes0 and serdes1 Siddharth Vadapalli
2025-04-17 12:34 ` kernel test robot [this message]
2025-04-17 12:32 ` [PATCH v3 4/4] arm64: dts: ti: k3-j722s-evm: drop redundant status within serdes0/serdes1 Siddharth Vadapalli
2025-04-18 18:57 ` [PATCH v3 0/4] J722S: Disable WIZ0 and WIZ1 in SoC file Nishanth Menon
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=aAD1SRN8CkYEvIof@4cfa58227a13 \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=s-vadapalli@ti.com \
--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