public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node
Date: Thu, 15 Dec 2022 23:14:22 +0800	[thread overview]
Message-ID: <Y5s5zroPehFNAmTt@416bcb91c936> (raw)
In-Reply-To: <Y5sz3Ax+tONdWgbN@dhcp22.suse.cz>

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] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node
Link: https://lore.kernel.org/stable/Y5sz3Ax%2BtONdWgbN%40dhcp22.suse.cz

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-12-15 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 22:21 [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call Mathieu Desnoyers
2022-12-14 23:16 ` Randy Dunlap
2022-12-15  6:34 ` Huang, Ying
2022-12-15  7:51 ` Michal Hocko
2022-12-15 13:57   ` Aneesh Kumar K.V
2022-12-15 14:33   ` Mathieu Desnoyers
2022-12-15 14:49     ` [PATCH] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node Michal Hocko
2022-12-15 15:14       ` kernel test robot [this message]
2022-12-15 20:00       ` Mathieu Desnoyers
2022-12-15 13:56 ` [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call Aneesh Kumar K.V

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=Y5s5zroPehFNAmTt@416bcb91c936 \
    --to=lkp@intel.com \
    --cc=mhocko@suse.com \
    --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