From: Jerome Glisse <jglisse@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 5141/5361] include/linux/hmm.h:102:22: error: field 'mmu_notifier' has incomplete type
Date: Fri, 1 Feb 2019 17:04:09 -0500 (EST) [thread overview]
Message-ID: <1540410520.100356979.1549058649241.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190201134737.9eaf0c69dc2584d2dc4ec4cc@linux-foundation.org>
> On Sat, 2 Feb 2019 00:14:13 +0800 kbuild test robot <lkp@intel.com> wrote:
>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > master
> > head: 9fe36dd579c794ae5f1c236293c55fb6847e9654
> > commit: a3402cb621c1b3908600d3f364e991a6c5a8c06e [5141/5361] mm/hmm:
> > improve driver API to work and wait over a range
> > config: x86_64-randconfig-b0-02012138 (attached as .config)
> > compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
> > reproduce:
> > git checkout a3402cb621c1b3908600d3f364e991a6c5a8c06e
> > # save the attached .config to linux build tree
> > make ARCH=x86_64
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from kernel/memremap.c:14:
> > >> include/linux/hmm.h:102:22: error: field 'mmu_notifier' has incomplete
> > >> type
> > struct mmu_notifier mmu_notifier;
>
> I can't reproduce this with that .config.
>
> hmm.h includes mmu_notifier.h so I can't eyeball why this would happen.
>
I am on pto, i will try to look it over in idle time can you send me
the config, or can i download it from somewhere ?
If i had to guess it is because this random config enable HMM without
any of the other HMM bits so adding: select MMU_NOTIFIER to config HMM
will fix it.
Cheers,
Jérôme
next prev parent reply other threads:[~2019-02-01 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 16:14 [linux-next:master 5141/5361] include/linux/hmm.h:102:22: error: field 'mmu_notifier' has incomplete type kbuild test robot
2019-02-01 21:47 ` Andrew Morton
2019-02-01 22:04 ` Jerome Glisse [this message]
2019-02-01 22:48 ` Balbir Singh
2019-02-01 23:08 ` Jerome Glisse
2019-02-02 0:16 ` Balbir Singh
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=1540410520.100356979.1549058649241.JavaMail.zimbra@redhat.com \
--to=jglisse@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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).