All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: wangyong <yongw.pur@gmail.com>
Cc: stable@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx
Date: Sat, 17 Sep 2022 01:09:26 +0800	[thread overview]
Message-ID: <YyStxmIX/EAhgG0C@facefcfb2e4a> (raw)
In-Reply-To: <1663347949-20389-2-git-send-email-wang.yong12@zte.com.cn>

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 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx
Link: https://lore.kernel.org/stable/1663347949-20389-2-git-send-email-wang.yong12%40zte.com.cn

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-09-16 17:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 13:09 [PATCH v4] page_alloc: consider highatomic reserve in watermark fast yong
2022-09-13 13:54 ` Greg KH
2022-09-14  0:46   ` yong w
2022-09-16  9:40     ` Greg KH
2022-09-16 17:05       ` [PATCH stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 wangyong
2022-09-16 17:05         ` [PATCH 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx wangyong
2022-09-16 17:09           ` kernel test robot [this message]
2022-09-16 17:05         ` [PATCH 2/3] page_alloc: consider highatomic reserve in watermark fast wangyong
2022-09-16 17:05         ` [PATCH 3/3] page_alloc: fix invalid watermark check on a negative value wangyong
2022-09-20 17:41         ` [PATCH stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 Greg KH
2022-09-25 10:35           ` [PATCH v2 " wangyong
2022-09-25 10:35             ` [PATCH v2 stable-4.19 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx wangyong
2022-09-25 10:36               ` kernel test robot
2022-09-25 11:00               ` Greg KH
2022-09-25 14:32                 ` yong w
2022-09-26  6:46                   ` Greg KH
2022-09-25 10:35             ` [PATCH v2 stable-4.19 2/3] page_alloc: consider highatomic reserve in watermark fast wangyong
2022-09-25 10:35             ` [PATCH v2 stable-4.19 3/3] page_alloc: fix invalid watermark check on a negative value wangyong
2022-10-02 15:37             ` [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 Greg KH
     [not found]               ` <CAOH5QeB2EqpqQd6fw-P199w8K8-3QNv_t-u_Wn1BLnfaSscmCg@mail.gmail.com>
2022-10-07 16:41                 ` Greg KH
2022-10-10 15:47                   ` yong w
2022-10-10 15:58                     ` Greg KH
2022-09-18  1:41       ` [PATCH v4] page_alloc: consider highatomic reserve in watermark fast Jaewon Kim
2022-09-19 13:21         ` yong w

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=YyStxmIX/EAhgG0C@facefcfb2e4a \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=stable@vger.kernel.org \
    --cc=yongw.pur@gmail.com \
    /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.