From: Lars-Peter Clausen <lars@metafoo.de>
To: eunb.song@samsung.com
Cc: "ralf@linux-mips.org" <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Fix build error crash_dump.c file.
Date: Thu, 02 May 2013 10:03:21 +0200 [thread overview]
Message-ID: <51821DC9.2010601@metafoo.de> (raw)
In-Reply-To: <21270808.191281367481634509.JavaMail.weblogic@epv6ml12>
On 05/02/2013 10:00 AM, EUNBONG SONG wrote:
>
> This patch fixes crash_dump.c build error.
>
When fixing a compile error/warning you should always include the error
message in the commit log.
> Signed-off-by: Eunbong Song <eunb.song@samsung.com>
> ---
> arch/mips/kernel/crash_dump.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/mips/kernel/crash_dump.c b/arch/mips/kernel/crash_dump.c
> index 35bed0d..3be9e7b 100644
> --- a/arch/mips/kernel/crash_dump.c
> +++ b/arch/mips/kernel/crash_dump.c
> @@ -2,6 +2,7 @@
> #include <linux/bootmem.h>
> #include <linux/crash_dump.h>
> #include <asm/uaccess.h>
> +#include <linux/slab.h>
>
> static int __init parse_savemaxmem(char *p)
> {
next prev parent reply other threads:[~2013-05-02 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 8:00 [PATCH] MIPS: Fix build error crash_dump.c file EUNBONG SONG
2013-05-02 8:03 ` Lars-Peter Clausen [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-02 8:25 [PATCH ] " EUNBONG SONG
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=51821DC9.2010601@metafoo.de \
--to=lars@metafoo.de \
--cc=eunb.song@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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