From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [memcg:since-3.6 14/227] drivers/media/video/vino.c:3953:35: error: 'VM_RESERVED' undeclared
Date: Fri, 12 Oct 2012 18:23:03 +0000 [thread overview]
Message-ID: <20121012182303.GA24093@localhost> (raw)
Hi Konstantin,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-3.6
head: 281983c5fb7e420ecf6c80074f7d4c2d3f330dd2
commit: aa011e456e6bd7e4179b03289d7501f8c8444809 [14/227] mm: kill vma flag VM_RESERVED and mm->reserved_vm counter
config: mips-allmodconfig # make ARCH=mips allmodconfig
All error/warnings:
drivers/media/video/vino.c: In function 'vino_mmap':
drivers/media/video/vino.c:3953:35: error: 'VM_RESERVED' undeclared (first use in this function)
drivers/media/video/vino.c:3953:35: note: each undeclared identifier is reported only once for each function it appears in
vim +3953 drivers/media/video/vino.c
d203a7ec Ralf Baechle 2005-09-06 3947 start += PAGE_SIZE;
d203a7ec Ralf Baechle 2005-09-06 3948 size -= PAGE_SIZE;
d203a7ec Ralf Baechle 2005-09-06 3949 }
d203a7ec Ralf Baechle 2005-09-06 3950
d203a7ec Ralf Baechle 2005-09-06 3951 fb->map_count = 1;
d203a7ec Ralf Baechle 2005-09-06 3952
d203a7ec Ralf Baechle 2005-09-06 @3953 vma->vm_flags |= VM_DONTEXPAND | VM_RESERVED;
d203a7ec Ralf Baechle 2005-09-06 3954 vma->vm_flags &= ~VM_IO;
d203a7ec Ralf Baechle 2005-09-06 3955 vma->vm_private_data = fb;
d203a7ec Ralf Baechle 2005-09-06 3956 vma->vm_file = file;
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
next reply other threads:[~2012-10-12 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 18:23 Fengguang Wu [this message]
2012-10-13 7:48 ` [memcg:since-3.6 14/227] drivers/media/video/vino.c:3953:35: error: 'VM_RESERVED' undeclared Konstantin Khlebnikov
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=20121012182303.GA24093@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.