From: Michel Lespinasse <walken@google.com>
To: kbuild test robot <fengguang.wu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [next:akpm 136/313] mm/mmap.c:1878:6: error: 'mm' undeclared
Date: Thu, 8 Nov 2012 22:21:50 -0800 [thread overview]
Message-ID: <20121109062150.GA7022@google.com> (raw)
In-Reply-To: <509c9bb9.+RUyEEi+hJKJghoL%fengguang.wu@intel.com>
On Fri, Nov 09, 2012 at 01:59:21PM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
> head: 6703d59701f7592c897b975de3952ba6bbb98b83
> commit: db877c95d306d688818542d49e9b63eb7a3b0894 [136/313] mm: augment vma rbtree with rb_subtree_gap
> config: make ARCH=ia64 alldefconfig
>
> All error/warnings:
>
> mm/mmap.c: In function 'expand_upwards':
> mm/mmap.c:1878:6: error: 'mm' undeclared (first use in this function)
> mm/mmap.c:1878:6: note: each undeclared identifier is reported only once for each function it appears in
commit 34550b95185c1ecfa8882664744c14edda385868
Author: Michel Lespinasse <walken@google.com>
Date: Thu Nov 8 22:14:34 2012 -0800
fix mm: augment vma rbtree with rb_subtree_gap
diff --git a/mm/mmap.c b/mm/mmap.c
index d12c69eaf23f..0b8f9d83e2e2 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2032,7 +2032,7 @@ int expand_upwards(struct vm_area_struct *vma, unsigned long address)
if (vma->vm_next)
vma_gap_update(vma->vm_next);
else
- mm->highest_vm_end = address;
+ vma->vm_mm->highest_vm_end = address;
perf_event_mmap(vma);
}
}
next parent reply other threads:[~2012-11-09 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <509c9bb9.+RUyEEi+hJKJghoL%fengguang.wu@intel.com>
2012-11-09 6:21 ` Michel Lespinasse [this message]
2012-11-11 23:42 ` [next:akpm 136/313] mm/mmap.c:1878:6: error: 'mm' undeclared 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=20121109062150.GA7022@google.com \
--to=walken@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox