From: kbuild test robot <fengguang.wu@intel.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: [mmotm:master 140/287] mm/page_alloc.c:6737:46: error: 'pgprot_t' has no member named 'pgprot'
Date: Sat, 30 Aug 2014 08:17:04 +0800 [thread overview]
Message-ID: <54011800.d8MKnT8qiZd6dbb6%fengguang.wu@intel.com> (raw)
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 8f1fc64dc9b39fedb7390e086001ce5ec327e80d
commit: 59f16a3915d3e5c6ddebc1b1c10ce0c14fd518cf [140/287] mm: introduce dump_vma
config: make ARCH=tile tilegx_defconfig
All error/warnings:
mm/page_alloc.c: In function 'dump_vma':
>> mm/page_alloc.c:6737:46: error: 'pgprot_t' has no member named 'pgprot'
vim +6737 mm/page_alloc.c
6731 printk(KERN_ALERT
6732 "vma %p start %p end %p\n"
6733 "next %p prev %p mm %p\n"
6734 "prot %lx anon_vma %p vm_ops %p\n"
6735 "pgoff %lx file %p private_data %p\n",
6736 vma, (void *)vma->vm_start, (void *)vma->vm_end, vma->vm_next,
> 6737 vma->vm_prev, vma->vm_mm, vma->vm_page_prot.pgprot,
6738 vma->anon_vma, vma->vm_ops, vma->vm_pgoff,
6739 vma->vm_file, vma->vm_private_data);
6740 dump_flags(vma->vm_flags, vmaflags_names, ARRAY_SIZE(vmaflags_names));
---
0-DAY kernel build testing backend Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-08-30 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 0:17 kbuild test robot [this message]
2014-08-31 2:43 ` Naoya Horiguchi
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=54011800.d8MKnT8qiZd6dbb6%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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