From: kernel test robot <lkp@intel.com>
To: Celeste Liu via B4 Relay <devnull+CoelacanthusHex.gmail.com@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] riscv/entry: get correct syscall number from syscall_get_nr()
Date: Thu, 17 Oct 2024 01:51:47 +0800 [thread overview]
Message-ID: <Zw_9MxsDnRFFSpdf@594376e94b8d> (raw)
In-Reply-To: <20241017-fix-riscv-syscall-nr-v1-1-4edb4ca07f07@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] riscv/entry: get correct syscall number from syscall_get_nr()
Link: https://lore.kernel.org/stable/20241017-fix-riscv-syscall-nr-v1-1-4edb4ca07f07%40gmail.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-16 17:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 17:49 [PATCH] riscv/entry: get correct syscall number from syscall_get_nr() Celeste Liu via B4 Relay
2024-10-16 17:51 ` kernel test robot [this message]
2024-10-21 14:00 ` Björn Töpel
2024-10-21 15:23 ` Celeste Liu
2024-10-21 16:46 ` Björn Töpel
2024-10-25 13:12 ` Thomas Gleixner
2024-10-25 14:30 ` Björn Töpel
2024-10-26 20:21 ` Thomas Gleixner
2024-10-27 15:29 ` Celeste Liu
2024-10-27 15:56 ` Thomas Gleixner
2024-10-27 17:01 ` Celeste Liu
2024-10-27 21:52 ` Thomas Gleixner
2024-10-28 0:17 ` Ron Economos
2024-10-28 16:25 ` Celeste Liu
2024-10-28 19:33 ` Björn Töpel
2024-11-30 22:39 ` Celeste Liu
2024-10-28 9:45 ` Björn Töpel
2024-11-15 21:49 ` Aurelien Jarno
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=Zw_9MxsDnRFFSpdf@594376e94b8d \
--to=lkp@intel.com \
--cc=devnull+CoelacanthusHex.gmail.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