linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Warren Turkal" <wt@penguintechs.org>
To: "Brad Boyer" <flar@allandria.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: [PATCH] Fix header include.
Date: Wed, 19 Nov 2008 18:30:54 -0800	[thread overview]
Message-ID: <e37d376a0811191830jc1e153ase47c798d928c90b2@mail.gmail.com> (raw)
In-Reply-To: <20081120004150.GA22395@cynthia.pants.nu>

I just submitted a patchset with more detailed commit comments.. It's
the same change wrapped in a, hopefully, prettier candy coating.

wt

On Wed, Nov 19, 2008 at 4:41 PM, Brad Boyer <flar@allandria.com> wrote:
> On Wed, Nov 19, 2008 at 02:51:40PM -0800, Andrew Morton wrote:
>> On Tue, 11 Nov 2008 12:56:48 -0800
>> Warren Turkal <wt@penguintechs.org> wrote:
>> > @@ -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) &&
>>
>> again: what was wrong with the old code??
>
> I just realized what you were asking after I sent my other reply. The
> include needs to move so 'struct hfsplus_vh' is declared before the
> function prototype. That happens in hfsplus_fs.h.
>
> My apologies for the noise, although I stand by my statement that I
> have no intention of actively maintaining this code myself.
>
>> If it was causing some compilation problem then please quote the compiler
>> output in the changelog.
>
> The original submitter would need to include the actual compiler output.
>
>        Brad Boyer
>        flar@allandria.com
>
>

  reply	other threads:[~2008-11-20  2:30 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     ` [PATCH] Fix header include Warren Turkal
2008-11-19 22:51       ` Andrew Morton
2008-11-19 23:01         ` Brad Boyer
2008-11-20  0:41         ` Brad Boyer
2008-11-20  2:30           ` Warren Turkal [this message]
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=e37d376a0811191830jc1e153ase47c798d928c90b2@mail.gmail.com \
    --to=wt@penguintechs.org \
    --cc=akpm@linux-foundation.org \
    --cc=flar@allandria.com \
    --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).