public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 3/3] mmap: Add clarifying comment to vma_merge() code
Date: Fri, 29 Sep 2023 01:17:36 +0800	[thread overview]
Message-ID: <ZRW1MBvWCCFevIg1@f61ccfac960a> (raw)
In-Reply-To: <20230928171634.2245042-4-Liam.Howlett@oracle.com>

Hi,

Thanks for your patch.

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

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

Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree.
Subject: [PATCH v2 3/3] mmap: Add clarifying comment to vma_merge() code
Link: https://lore.kernel.org/stable/20230928171634.2245042-4-Liam.Howlett%40oracle.com

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




  reply	other threads:[~2023-09-28 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 17:16 [PATCH 0/3] Fixes for vma_merge() error path Liam R. Howlett
2023-09-28 17:16 ` [PATCH v2 1/3] mmap: Fix vma_iterator in error path of vma_merge() Liam R. Howlett
2023-09-28 17:16 ` [PATCH v2 2/3] mmap: Fix error paths with dup_anon_vma() Liam R. Howlett
2023-09-28 17:16 ` [PATCH v2 3/3] mmap: Add clarifying comment to vma_merge() code Liam R. Howlett
2023-09-28 17:17   ` kernel test robot [this message]
2023-09-28 17:26     ` Liam R. Howlett
2023-09-29  5:52       ` Greg KH
2023-09-29 10:29   ` Vlastimil Babka

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=ZRW1MBvWCCFevIg1@f61ccfac960a \
    --to=lkp@intel.com \
    --cc=Liam.Howlett@oracle.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