From: Alistair Popple <apopple@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: stable@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH v3 3/3] selftests/hmm-tests: Add test for dirty bits
Date: Wed, 24 Aug 2022 14:24:51 +1000 [thread overview]
Message-ID: <871qt6gtc1.fsf@nvdebian.thelocal> (raw)
In-Reply-To: <YwWVp83+9Wd5GbCV@b1a0c294b6c5>
kernel test robot <lkp@intel.com> writes:
> 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 v3 3/3] selftests/hmm-tests: Add test for dirty bits
> Link: https://lore.kernel.org/stable/8e425a8ec191682fa2036260c575f065eeb56a53.1661309831.git-series.apopple%40nvidia.com
>
> The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Ugh. I didn't mean to Cc stable on this patch, just the first two.
- Alistair
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Popple <apopple@nvidia.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 3/3] selftests/hmm-tests: Add test for dirty bits
Date: Wed, 24 Aug 2022 14:24:51 +1000 [thread overview]
Message-ID: <871qt6gtc1.fsf@nvdebian.thelocal> (raw)
In-Reply-To: <YwWVp83+9Wd5GbCV@b1a0c294b6c5>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
kernel test robot <lkp@intel.com> writes:
> Hi,
>
> Thanks for your patch.
>
> FYI: kernel test robot notices the stable kernel rule is not satisfied.
>
> Rule: 'Cc: stable(a)vger.kernel.org' or 'commit <sha1> upstream.'
> Subject: [PATCH v3 3/3] selftests/hmm-tests: Add test for dirty bits
> Link: https://lore.kernel.org/stable/8e425a8ec191682fa2036260c575f065eeb56a53.1661309831.git-series.apopple%40nvidia.com
>
> The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Ugh. I didn't mean to Cc stable on this patch, just the first two.
- Alistair
next prev parent reply other threads:[~2022-08-24 4:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 3:03 [PATCH v3 1/3] mm/migrate_device.c: Flush TLB while holding PTL Alistair Popple
2022-08-24 3:03 ` Alistair Popple
2022-08-24 3:03 ` [PATCH v3 2/3] mm/migrate_device.c: Copy pte dirty bit to page Alistair Popple
2022-08-24 3:03 ` Alistair Popple
2022-08-24 15:39 ` Peter Xu
2022-08-24 15:39 ` Peter Xu
2022-08-25 22:21 ` Alistair Popple
2022-08-25 22:21 ` Alistair Popple
2022-08-25 23:27 ` Peter Xu
2022-08-25 23:27 ` Peter Xu
2022-08-26 1:02 ` Alistair Popple
2022-08-26 1:02 ` Alistair Popple
2022-08-26 1:14 ` Huang, Ying
2022-08-26 1:14 ` Huang, Ying
2022-08-26 14:32 ` Peter Xu
2022-08-26 14:32 ` Peter Xu
2022-08-26 14:47 ` David Hildenbrand
2022-08-26 14:47 ` David Hildenbrand
2022-08-26 15:55 ` Peter Xu
2022-08-26 15:55 ` Peter Xu
2022-08-26 16:46 ` David Hildenbrand
2022-08-26 16:46 ` David Hildenbrand
2022-08-26 21:37 ` Peter Xu
2022-08-26 21:37 ` Peter Xu
2022-08-26 22:19 ` David Hildenbrand
2022-08-26 22:19 ` David Hildenbrand
2022-08-24 3:03 ` [PATCH v3 3/3] selftests/hmm-tests: Add test for dirty bits Alistair Popple
2022-08-24 3:03 ` Alistair Popple
2022-08-24 3:06 ` kernel test robot
2022-08-24 4:24 ` Alistair Popple [this message]
2022-08-24 4:24 ` Alistair Popple
2022-08-24 8:21 ` [PATCH v3 1/3] mm/migrate_device.c: Flush TLB while holding PTL David Hildenbrand
2022-08-24 8:21 ` David Hildenbrand
2022-08-24 12:26 ` Alistair Popple
2022-08-24 12:26 ` Alistair Popple
2022-08-24 12:35 ` David Hildenbrand
2022-08-24 12:35 ` David Hildenbrand
2022-08-25 1:36 ` Huang, Ying
2022-08-25 1:36 ` Huang, Ying
2022-08-25 22:35 ` Alistair Popple
2022-08-25 22:35 ` Alistair Popple
2022-08-26 0:56 ` Huang, Ying
2022-08-26 0:56 ` Huang, Ying
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=871qt6gtc1.fsf@nvdebian.thelocal \
--to=apopple@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.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 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.