From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Sasha Levin <sashal@kernel.org>Sasha Levin <sashal@kernel.org>,
dan.j.williams@intel.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, stable@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [PATCH v2] mm: Fix modifying of page protection by insert_pfn_pmd()
Date: Tue, 09 Apr 2019 10:16:59 +0530 [thread overview]
Message-ID: <87o95fn5to.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190403122939.C4187214AF@mail.kernel.org>
Sasha Levin <sashal@kernel.org> writes:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.0.5, v4.19.32, v4.14.109, v4.9.166, v4.4.177, v3.18.137.
>
> v5.0.5: Build OK!
> v4.19.32: Build OK!
Considering this only impact ppc64 for now I guess it is ok to apply
this to the above two kernel versions. The SCM support for ppc64 was
added via
git describe --contains b5beae5e224f1c72c4482b0ab36fc3d89481a6b2
v4.20-rc1~24^2~68
powerpc/pseries: Add driver for PAPR SCM regions
-aneesh
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Sasha Levin <sashal@kernel.org>, Sasha Levin <sashal@kernel.org>,
dan.j.williams@intel.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, stable@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [PATCH v2] mm: Fix modifying of page protection by insert_pfn_pmd()
Date: Tue, 09 Apr 2019 10:16:59 +0530 [thread overview]
Message-ID: <87o95fn5to.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190403122939.C4187214AF@mail.kernel.org>
Sasha Levin <sashal@kernel.org> writes:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.0.5, v4.19.32, v4.14.109, v4.9.166, v4.4.177, v3.18.137.
>
> v5.0.5: Build OK!
> v4.19.32: Build OK!
Considering this only impact ppc64 for now I guess it is ok to apply
this to the above two kernel versions. The SCM support for ppc64 was
added via
git describe --contains b5beae5e224f1c72c4482b0ab36fc3d89481a6b2
v4.20-rc1~24^2~68
powerpc/pseries: Add driver for PAPR SCM regions
-aneesh
next prev parent reply other threads:[~2019-04-09 4:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:51 [PATCH v2] mm: Fix modifying of page protection by insert_pfn_pmd() Aneesh Kumar K.V
2019-04-02 11:51 ` Aneesh Kumar K.V
2019-04-02 15:24 ` Jan Kara
2019-04-02 15:24 ` Jan Kara
2019-04-02 15:24 ` Jan Kara
2019-04-03 12:29 ` Sasha Levin
2019-04-03 12:29 ` Sasha Levin
2019-04-09 4:46 ` Aneesh Kumar K.V [this message]
2019-04-09 4:46 ` Aneesh Kumar K.V
2019-04-24 17:13 ` Dan Williams
2019-04-24 17:13 ` Dan Williams
2019-04-24 17:13 ` Dan Williams
2019-04-24 17:38 ` Matthew Wilcox
2019-04-24 17:38 ` Matthew Wilcox
2019-04-24 17:38 ` Matthew Wilcox
2019-04-24 18:13 ` Dan Williams
2019-04-24 18:13 ` Dan Williams
2019-04-24 18:13 ` Dan Williams
2019-04-25 1:37 ` Aneesh Kumar K.V
2019-04-25 1:37 ` Aneesh Kumar K.V
2019-04-25 1:37 ` Aneesh Kumar K.V
2019-04-25 4:33 ` Dan Williams
2019-04-25 4:33 ` Dan Williams
2019-04-25 4:33 ` Dan Williams
2019-04-25 7:31 ` Jan Kara
2019-04-25 7:31 ` Jan Kara
2019-04-25 7:31 ` Jan Kara
2019-04-26 0:33 ` Dan Williams
2019-04-26 0:33 ` Dan Williams
2019-04-26 0:33 ` Dan Williams
2019-04-26 0:51 ` Matthew Wilcox
2019-04-26 0:51 ` Matthew Wilcox
2019-04-26 0:51 ` Matthew Wilcox
2019-04-26 8:36 ` Jan Kara
2019-04-26 8:36 ` Jan Kara
2019-04-26 8:36 ` Jan Kara
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=87o95fn5to.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=sashal@kernel.org \
--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.