From: kernel test robot <lkp@intel.com>
To: Dave Vasilevsky via B4 Relay <devnull+dave.vasilevsky.ca@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] powerpc: Fix mprotect on book3s32
Date: Tue, 28 Oct 2025 07:28:07 +0800 [thread overview]
Message-ID: <aQAAB56SHIng8CGt@fb33b90f3739> (raw)
In-Reply-To: <20251027-vasi-mprotect-g3-v1-1-3c5187085f9a@vasilevsky.ca>
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] powerpc: Fix mprotect on book3s32
Link: https://lore.kernel.org/stable/20251027-vasi-mprotect-g3-v1-1-3c5187085f9a%40vasilevsky.ca
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-27 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 23:21 [PATCH] powerpc: Fix mprotect on book3s32 Dave Vasilevsky via B4 Relay
2025-10-27 23:28 ` kernel test robot [this message]
2025-11-08 19:16 ` Ritesh Harjani
2025-11-08 22:24 ` Dave Vasilevsky
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=aQAAB56SHIng8CGt@fb33b90f3739 \
--to=lkp@intel.com \
--cc=devnull+dave.vasilevsky.ca@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;
as well as URLs for NNTP newsgroup(s).