From: Qais Yousef <qais.yousef@imgtec.com>
To: <linux-kernel@vger.kernel.org>
Cc: Qais Yousef <qais.yousef@imgtec.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
Vivek Goyal <vgoyal@redhat.com>, <linux-mips@linux-mips.org>,
<stable@vger.kernel.org>
Subject: [PATCH] crash_dump: fix compilation error (on MIPS at least)
Date: Wed, 4 Dec 2013 15:58:22 +0000 [thread overview]
Message-ID: <1386172702-31266-1-git-send-email-qais.yousef@imgtec.com> (raw)
In file included from kernel/crash_dump.c:2:0:
include/linux/crash_dump.h:22:27: error: unknown type name ‘pgprot_t’
when CONFIG_CRASH_DUMP=y
The error was traced back to this commit:
9cb218131de1 vmcore: introduce remap_oldmem_pfn_range()
include <asm/pgtable.h> to get the missing definition
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: <linux-mips@linux-mips.org>
Cc: <stable@vger.kernel.org> # 3.12
Reviewed-by: James Hogan <james.hogan@imgtec.com>
Signed-off-by: Qais Yousef <qais.yousef@imgtec.com>
---
I haven't tried any other architecture except mips.
If OK this should be considered for stable 3.12 (CCed).
include/linux/crash_dump.h | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/include/linux/crash_dump.h b/include/linux/crash_dump.h
index fe68a5a..7032518 100644
--- a/include/linux/crash_dump.h
+++ b/include/linux/crash_dump.h
@@ -6,6 +6,8 @@
#include <linux/proc_fs.h>
#include <linux/elf.h>
+#include <asm/pgtable.h> /* for pgprot_t */
+
#define ELFCORE_ADDR_MAX (-1ULL)
#define ELFCORE_ADDR_ERR (-2ULL)
--
1.7.1
next reply other threads:[~2013-12-04 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 15:58 Qais Yousef [this message]
2013-12-04 21:30 ` Vivek Goyal
2013-12-05 8:52 ` Qais Yousef
2013-12-05 13:58 ` Vivek Goyal
2013-12-11 11:43 ` Qais Yousef
2013-12-12 14:42 ` Vivek Goyal
2014-01-08 16:22 ` Qais Yousef
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=1386172702-31266-1-git-send-email-qais.yousef@imgtec.com \
--to=qais.yousef@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=stable@vger.kernel.org \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®