From: Ralph Campbell <rcampbell@nvidia.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Aug 6 (mm/migrate.c)
Date: Thu, 6 Aug 2020 10:13:39 -0700 [thread overview]
Message-ID: <1634e188-0faf-a240-6847-94468d63d7d7@nvidia.com> (raw)
In-Reply-To: <85e9276d-1747-b265-53be-a33ab6203045@infradead.org>
On 8/6/20 7:50 AM, Randy Dunlap wrote:
> On 8/5/20 11:21 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>
> on x86_64:
>
> when CONFIG_MMU_NOTIFIER is not set/enabled:
>
> ../mm/migrate.c: In function 'migrate_vma_collect':
> ../mm/migrate.c:2481:7: error: 'struct mmu_notifier_range' has no member named 'migrate_pgmap_owner'
> range.migrate_pgmap_owner = migrate->pgmap_owner;
> ^
>
Thanks for finding this.
I'm working on it.
prev parent reply other threads:[~2020-08-06 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200806162116.1d033db0@canb.auug.org.au>
2020-08-06 14:50 ` Randy Dunlap
2020-08-06 17:13 ` Ralph Campbell [this message]
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=1634e188-0faf-a240-6847-94468d63d7d7@nvidia.com \
--to=rcampbell@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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