From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH] f2fs: add missing pretech.h include
Date: Thu, 27 Dec 2012 15:30:32 +0100 [thread overview]
Message-ID: <20121227143032.GA3223@osiris> (raw)
>From aa027f06dfb5b2fd27d6f92391d8340df671e82b Mon Sep 17 00:00:00 2001
From: Heiko Carstens <heiko.carstens@de.ibm.com>
Date: Thu, 27 Dec 2012 15:22:27 +0100
Subject: [PATCH] f2fs: add missing pretech.h include
Fix these compile errors on s390:
fs/f2fs/data.c: In function 'read_end_io':
fs/f2fs/data.c:311:4: error: implicit declaration of function 'prefetchw' [-Werror=implicit-function-declaration]
fs/f2fs/segment.c: In function 'f2fs_end_io_write':
fs/f2fs/segment.c:628:4: error: implicit declaration of function 'prefetchw' [-Werror=implicit-function-declaration]
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
---
fs/f2fs/data.c | 1 +
fs/f2fs/segment.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 655aeab..f5d2c62 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -13,6 +13,7 @@
#include <linux/buffer_head.h>
#include <linux/mpage.h>
#include <linux/writeback.h>
+#include <linux/prefetch.h>
#include <linux/backing-dev.h>
#include <linux/blkdev.h>
#include <linux/bio.h>
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 1b26e4e..cc28975 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -12,6 +12,7 @@
#include <linux/f2fs_fs.h>
#include <linux/bio.h>
#include <linux/blkdev.h>
+#include <linux/prefetch.h>
#include <linux/vmalloc.h>
#include "f2fs.h"
--
1.7.12.4
next reply other threads:[~2012-12-27 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 14:30 Heiko Carstens [this message]
2012-12-27 14:34 ` [PATCH] f2fs: add missing pretech.h include Heiko Carstens
2012-12-28 0:48 ` Jaegeuk Kim
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=20121227143032.GA3223@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.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;
as well as URLs for NNTP newsgroup(s).