From: Greg KH <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: kernel test robot <rong.a.chen@intel.com>,
Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, lkp <lkp@intel.com>
Subject: Re: Fwd: warning: stable kernel rule is not satisfied
Date: Mon, 8 Aug 2022 10:23:12 +0200 [thread overview]
Message-ID: <YvDH8FmikusK2yFy@kroah.com> (raw)
In-Reply-To: <7d749ba8-e1e7-6614-a5f6-abaeebd2691d@gmail.com>
On Mon, Aug 08, 2022 at 03:12:36PM +0700, Bagas Sanjaya wrote:
> On 8/8/22 09:51, kernel test robot wrote:
> > -------- Forwarded Message --------
> > Subject: warning: stable kernel rule is not satisfied
> > <snip>
> >
> > 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 5.10] block: fix null-deref in percpu_ref_put
> > Link: https://lore.kernel.org/stable/20220729065243.1786222-1-zhangwensheng%40huaweicloud.com
> >
> > The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> >
>
> Sasha uses "[ Upstream commit <sha1> ]", so his syntax should be
> accepted, too.
That's not the "rule" that is being checked here at all from what I have
seen so far when this email has been sent out.
thanks,
greg k-h
prev parent reply other threads:[~2022-08-08 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YuOFhUb9VRGxk6jh@a446980b915c>
2022-07-29 7:28 ` warning: stable kernel rule is not satisfied kernel test robot
2022-08-08 2:51 ` Fwd: " kernel test robot
2022-08-08 6:02 ` Greg KH
2022-08-08 6:15 ` Chen, Rong A
2022-08-08 8:12 ` Bagas Sanjaya
2022-08-08 8:23 ` Greg KH [this message]
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=YvDH8FmikusK2yFy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=lkp@intel.com \
--cc=rong.a.chen@intel.com \
--cc=sashal@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.