From: akpm@linux-foundation.org
To: gcosta@redhat.com, mm-commits@vger.kernel.org
Subject: - mm-sparse-vmemmapc-make-sure-init_mm-is-included.patch removed from -mm tree
Date: Tue, 30 Oct 2007 11:06:27 -0700 [thread overview]
Message-ID: <200710301806.l9UI6Rmo020522@imap1.linux-foundation.org> (raw)
The patch titled
mm/sparse-vmemmap.c: make sure init_mm is included
has been removed from the -mm tree. Its filename was
mm-sparse-vmemmapc-make-sure-init_mm-is-included.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: mm/sparse-vmemmap.c: make sure init_mm is included
From: Glauber de Oliveira Costa <gcosta@redhat.com>
mm/sparse-vmemmap.c uses init_mm in some places. However, it is not
present in any of the headers currently included in the file.
init_mm is defined as extern in sched.h, so we add it to the headers list
Up to now, this problem was masked by the fact that functions like
set_pte_at() and pmd_populate_kernel() are usually macros that expand to
simpler variants that does not use the first parameter at all.
Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/sparse-vmemmap.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/sparse-vmemmap.c~mm-sparse-vmemmapc-make-sure-init_mm-is-included mm/sparse-vmemmap.c
--- a/mm/sparse-vmemmap.c~mm-sparse-vmemmapc-make-sure-init_mm-is-included
+++ a/mm/sparse-vmemmap.c
@@ -24,6 +24,7 @@
#include <linux/module.h>
#include <linux/spinlock.h>
#include <linux/vmalloc.h>
+#include <linux/sched.h>
#include <asm/dma.h>
#include <asm/pgalloc.h>
#include <asm/pgtable.h>
_
Patches currently in -mm which might be from gcosta@redhat.com are
origin.patch
git-kvm.patch
reply other threads:[~2007-10-30 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200710301806.l9UI6Rmo020522@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gcosta@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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.