Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yuanzheng Song <songyuanzheng@huawei.com>
Cc: stable@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH STABLE 5.10] mm/memory: add non-anonymous page check in the copy_present_page()
Date: Mon, 24 Oct 2022 17:25:30 +0800	[thread overview]
Message-ID: <Y1ZaChUEi/qBCEFa@dba927f25f90> (raw)
In-Reply-To: <20221024094911.3054769-1-songyuanzheng@huawei.com>

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 STABLE 5.10] mm/memory: add non-anonymous page check in the copy_present_page()
Link: https://lore.kernel.org/stable/20221024094911.3054769-1-songyuanzheng%40huawei.com

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

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp




  reply	other threads:[~2022-10-24  9:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  9:49 [PATCH STABLE 5.10] mm/memory: add non-anonymous page check in the copy_present_page() Yuanzheng Song
2022-10-24  9:25 ` kernel test robot [this message]
2022-10-26 16:52 ` Greg KH
2022-10-27 11:37   ` songyuanzheng
2022-10-26 21:51 ` Hugh Dickins
2022-10-27  0:32   ` Peter Xu
2022-10-27  1:48     ` Hugh Dickins
2022-10-27  2:11       ` songyuanzheng
2022-10-27 15:01       ` Peter Xu
     [not found]         ` <8aad435-bdc6-816f-2fe4-efe53abd6e5@google.com>
     [not found]           ` <Y1sMk30wS+1uH/hc@x1n>
2022-10-28  1:32             ` Hugh Dickins
2022-10-28  4:26               ` David Hildenbrand
2022-10-28 14:39               ` Peter Xu
2022-10-27  7:54   ` David Hildenbrand
2022-10-27 11:55   ` songyuanzheng

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=Y1ZaChUEi/qBCEFa@dba927f25f90 \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=songyuanzheng@huawei.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