From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@lst•de>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: build failure after merge of the dma-mapping-fixes tree
Date: Thu, 8 Aug 2019 08:29:48 +1000 [thread overview]
Message-ID: <20190808082948.781f0033@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
Hi all,
After merging the dma-mapping-fixes tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
/home/sfr/next/next/mm/migrate.c: In function 'migrate_vma_collect':
/home/sfr/next/next/mm/migrate.c:2350:61: error: 'mm_walk' undeclared (first use in this function)
mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, NULL, mm_walk.mm,
^~~~~~~
Caused by commit
f4c1f66bf710 ("pagewalk: seperate function pointers from iterator data")
I have applied the following patch for today:
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Thu, 8 Aug 2019 08:25:40 +1000
Subject: [PATCH] pagewalk: fix up missed conversion in migrate_vma_collect()
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
mm/migrate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/migrate.c b/mm/migrate.c
index 75de4378dfcd..585113d2e37d 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -2347,7 +2347,7 @@ static void migrate_vma_collect(struct migrate_vma *migrate)
{
struct mmu_notifier_range range;
- mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, NULL, mm_walk.mm,
+ mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, NULL, migrate->vma->vm_mm,
migrate->start,
migrate->end);
mmu_notifier_invalidate_range_start(&range);
--
2.20.1
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-07 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 22:29 Stephen Rothwell [this message]
2019-08-07 22:37 ` linux-next: build failure after merge of the dma-mapping-fixes tree Christoph Hellwig
2019-08-08 0:42 ` Stephen Rothwell
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=20190808082948.781f0033@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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