Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] tick/common: Align tick period during sched_timer setup.
Date: Thu, 15 Jun 2023 17:19:52 +0800	[thread overview]
Message-ID: <ZIrXuAcuD3ifejE2@b4e643f4d690> (raw)
In-Reply-To: <20230615091830.RxMV2xf_@linutronix.de>

Hi,

Thanks for your patch.

FYI: kernel test robot notices the stable kernel rule is not satisfied.

Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
Subject: [PATCH] tick/common: Align tick period during sched_timer setup.
Link: https://lore.kernel.org/stable/20230615091830.RxMV2xf_%40linutronix.de

The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

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




  reply	other threads:[~2023-06-15  9:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12c6f9a3-d087-b824-0d05-0d18c9bc1bf3@amazon.com>
2023-06-13 18:58 ` Observing RCU stalls in kernel 5.4/5.10/5.15/6.1 stable trees Bhatnagar, Rishabh
2023-06-14  9:14   ` gregkh
2023-06-14 13:08     ` Luiz Capitulino
2023-06-14  9:14   ` gregkh
2023-06-14  9:20     ` Sebastian Andrzej Siewior
2023-06-14 13:10       ` Luiz Capitulino
2023-06-14 13:45         ` Sven-Haegar Koch
2023-06-14 13:57           ` Luiz Capitulino
2023-06-14 14:30             ` Mathias Krause
2023-06-15  9:18               ` [PATCH] tick/common: Align tick period during sched_timer setup Sebastian Andrzej Siewior
2023-06-15  9:19                 ` kernel test robot [this message]
2023-06-15 11:13                 ` Mathias Krause
2023-06-15 12:20                 ` Richard W.M. Jones
2023-06-15 14:15                 ` Luiz Capitulino
2023-06-15 16:00                 ` SeongJae Park
2023-06-19  6:18                 ` Greg KH
2023-06-19  7:03                   ` Mathias Krause

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=ZIrXuAcuD3ifejE2@b4e643f4d690 \
    --to=lkp@intel.com \
    --cc=bigeasy@linutronix.de \
    --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