From: Warren Turkal <wt@penguintechs.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Warren Turkal <wt@penguintechs.org>
Subject: [PATCH] Fix header include.
Date: Tue, 11 Nov 2008 12:56:48 -0800 [thread overview]
Message-ID: <1226437008-14247-4-git-send-email-wt@penguintechs.org> (raw)
In-Reply-To: <1226437008-14247-3-git-send-email-wt@penguintechs.org>
Signed-off-by: Warren Turkal <wt@penguintechs.org>
---
fs/hfsplus/super.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/hfsplus/super.c b/fs/hfsplus/super.c
index 128101b..4f00a84 100644
--- a/fs/hfsplus/super.c
+++ b/fs/hfsplus/super.c
@@ -15,12 +15,12 @@
#include <linux/vfs.h>
#include <linux/nls.h>
+#include "hfsplus_fs.h"
+
static struct inode *hfsplus_alloc_inode(struct super_block *sb);
static void hfsplus_destroy_inode(struct inode *inode);
static bool hfsplus_vol_has_journal(struct hfsplus_vh *vhdr);
-#include "hfsplus_fs.h"
-
static bool hfsplus_vol_has_journal(struct hfsplus_vh *vhdr)
{
return (vhdr->attributes & cpu_to_be32(HFSPLUS_VOL_JOURNALED) &&
--
1.5.6.3
next prev parent reply other threads:[~2008-11-11 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:56 hfsplus journal detection - try 4 Warren Turkal
2008-11-11 20:56 ` [PATCH] Identify journal info block in volume header Warren Turkal
2008-11-11 20:56 ` [PATCH] Fix journal detection on HFS+ Warren Turkal
2008-11-11 20:56 ` Warren Turkal [this message]
2008-11-19 22:51 ` [PATCH] Fix header include Andrew Morton
2008-11-19 23:01 ` Brad Boyer
2008-11-20 0:41 ` Brad Boyer
2008-11-20 2:30 ` Warren Turkal
2008-11-19 22:51 ` [PATCH] Fix journal detection on HFS+ Andrew Morton
2008-11-20 1:01 ` Warren Turkal
2008-11-19 22:49 ` [PATCH] Identify journal info block in volume header Andrew Morton
2008-11-19 7:07 ` hfsplus journal detection - try 4 Warren Turkal
2008-11-19 8:39 ` Jörn Engel
2008-11-19 22:36 ` Warren Turkal
2008-11-19 22:49 ` Andrew Morton
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=1226437008-14247-4-git-send-email-wt@penguintechs.org \
--to=wt@penguintechs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).