From: "Warren Turkal" <wt@penguintechs.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix journal detection on HFS+.
Date: Thu, 20 Nov 2008 09:02:26 -0800 [thread overview]
Message-ID: <e37d376a0811200902hdd0a338u9f73ae8a0ccbee7e@mail.gmail.com> (raw)
In-Reply-To: <20081120112903.GB30887@logfs.org>
On Thu, Nov 20, 2008 at 3:29 AM, Jörn Engel <joern@logfs.org> wrote:
> On Wed, 19 November 2008 18:26:00 -0800, Warren Turkal wrote:
>>
>> diff --git a/fs/hfsplus/super.c b/fs/hfsplus/super.c
>> index eb74531..4f00a84 100644
>> --- a/fs/hfsplus/super.c
>> +++ b/fs/hfsplus/super.c
>> @@ -15,10 +15,17 @@
>> #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);
>
> Sorry for not noticing this before. The function declaration is
> unnecessary. There are no callers before the actual function
> definition, which is just below.
I will have to get rid of this when I get home tonight.
>> -#include "hfsplus_fs.h"
>> +static bool hfsplus_vol_has_journal(struct hfsplus_vh *vhdr)
>> +{
>> + return (vhdr->attributes & cpu_to_be32(HFSPLUS_VOL_JOURNALED) &&
>> + vhdr->journal_info_block);
>> +}
>
> You're going through a huge number of iterations for such a simple
> change. Others would have lost patience some time ago. :(
Bah...I'm playing in someone else's sandbox, and I have a lot to learn
around here. I figure I probably shouldn't second guess the more
experienced folks.
wt
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-20 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 2:25 [PATCH 0/2] HFS+ journal improvement - take 5 Warren Turkal
2008-11-20 2:25 ` [PATCH 1/2] Identify journal info block in volume header Warren Turkal
2008-11-20 2:26 ` [PATCH 2/2] Fix journal detection on HFS+ Warren Turkal
2008-11-20 11:29 ` Jörn Engel
2008-11-20 17:02 ` Warren Turkal [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 4:01 [PATCH 0/2] HFS+ journal improvement - take 6 Warren Turkal
2008-11-21 4:01 ` [PATCH 1/2] Identify journal info block in volume header Warren Turkal
2008-11-21 4:01 ` [PATCH 2/2] Fix journal detection on HFS+ Warren Turkal
2008-11-23 4:52 ` Roman Zippel
2008-11-25 23:45 ` Warren Turkal
2008-11-27 16:21 ` Roman Zippel
2008-12-01 10:28 ` Warren Turkal
2008-12-01 14:27 ` Roman Zippel
2008-12-01 14:49 ` Roman Zippel
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=e37d376a0811200902hdd0a338u9f73ae8a0ccbee7e@mail.gmail.com \
--to=wt@penguintechs.org \
--cc=akpm@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@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 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).