From: akpm@linux-foundation.org
To: arnd@arndb.de, jhubbard@nvidia.com, mm-commits@vger.kernel.org,
steven.price@arm.com
Subject: [folded-merged] mm-pagewalk-add-p4d_entry-and-pgd_entry-fix.patch removed from -mm tree
Date: Mon, 03 Feb 2020 17:10:52 -0800 [thread overview]
Message-ID: <20200204011052.teSYyWB3h%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm: pagewalk: fix unused variable warning
has been removed from the -mm tree. Its filename was
mm-pagewalk-add-p4d_entry-and-pgd_entry-fix.patch
This patch was dropped because it was folded into mm-pagewalk-add-p4d_entry-and-pgd_entry.patch
------------------------------------------------------
From: Arnd Bergmann <arnd@arndb.de>
Subject: mm: pagewalk: fix unused variable warning
One of the pagewalk patches introduced a harmless warning:
mm/hmm.c: In function 'hmm_vma_walk_pud':
mm/hmm.c:478:9: error: unused variable 'pmdp' [-Werror=3Dunused-variable]
pmd_t *pmdp;
^~~~
mm/hmm.c:477:30: error: unused variable 'next' [-Werror=3Dunused-variable=
]
unsigned long addr =3D start, next;
^~~~
Remove both of the now-unused variables.
Link: http://lkml.kernel.org/r/20200107204607.1533842-1-arnd@arndb.de
Fixes: cb4d03d5fb4c ("mm: pagewalk: add p4d_entry() and pgd_entry()")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
Reviewed-by: Steven Price <steven.price@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/hmm.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/mm/hmm.c~mm-pagewalk-add-p4d_entry-and-pgd_entry-fix
+++ a/mm/hmm.c
@@ -474,8 +474,7 @@ static int hmm_vma_walk_pud(pud_t *pudp,
{
struct hmm_vma_walk *hmm_vma_walk = walk->private;
struct hmm_range *range = hmm_vma_walk->range;
- unsigned long addr = start, next;
- pmd_t *pmdp;
+ unsigned long addr = start;
pud_t pud;
int ret = 0;
spinlock_t *ptl = pud_trans_huge_lock(pudp, walk->vma);
_
Patches currently in -mm which might be from arnd@arndb.de are
mm-pagewalk-add-p4d_entry-and-pgd_entry.patch
reply other threads:[~2020-02-04 1:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200204011052.teSYyWB3h%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=steven.price@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).