All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: "J.A. Magallon" <jamagallon@able.es>,
	linux-hfsplus-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] new HFS(+) driver
Date: Sat, 4 Oct 2003 00:39:04 +0200	[thread overview]
Message-ID: <20031003223904.GE30751@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0310031227460.17548-100000@serv> (from zippel@linux-m68k.org on Fri, Oct 03, 2003 at 12:30:36 +0200)


On 10.03, Roman Zippel wrote:
> Hi,
> 
> On Fri, 3 Oct 2003, J.A. Magallon wrote:
> 
> > Two notes:
> > - You should give a patch or at least give a notice that linux/include/hfs* have
> >   to be killed (or move hfs_fs.h there).
> 
> You did apply linux-2.4.hfs.diff? I don't understand why you had to move 
> hfs_fs.h, it should be picked up from the current directory.
> 

I applied it, it just keeps mainstream files from including old hfs* files
in include/linux, but the old files stay around (you end with two
versions of hfs_fs.h, one in include/linux and other in fs/hfs...)
I did not move anything, just deleted those old files. But as other
filesystems put their xxxx_fs.h in include/linux, I thought that
perhaps hfs(plus) should do the same.

> > - I had to include linux/sched.h in hfs/sysdep.c to get the definition for
> >   'current', that was neded in some subinclude of linux/smp_lock. This can be
> >   caused by any other of my patches, but it doesn't hurt.
> 
> Simply move <linux/smp_lock.h> past "hfs_fs.h".
> 

Thanks.

-- 
J.A. Magallon <jamagallon()able!es>     \                 Software is like sex:
werewolf!able!es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.23-pre6-jam1 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk))

WARNING: multiple messages have this Message-ID (diff)
From: "J.A. Magallon" <jamagallon=cer70A47DaU@public.gmane.org>
To: Roman Zippel <zippel=Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
Cc: "J.A. Magallon" <jamagallon=cer70A47DaU@public.gmane.org>,
	linux-hfsplus-devel=5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-fsdevel=u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel=u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [ANNOUNCE] new HFS(+) driver
Date: Sat, 4 Oct 2003 00:39:04 +0200	[thread overview]
Message-ID: <20031003223904.GE30751@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0310031227460.17548-100000@serv> (from zippel@linux-m68k.org on Fri, Oct 03, 2003 at 12:30:36 +0200)


On 10.03, Roman Zippel wrote:
> Hi,
> 
> On Fri, 3 Oct 2003, J.A. Magallon wrote:
> 
> > Two notes:
> > - You should give a patch or at least give a notice that linux/include/hfs* have
> >   to be killed (or move hfs_fs.h there).
> 
> You did apply linux-2.4.hfs.diff? I don't understand why you had to move 
> hfs_fs.h, it should be picked up from the current directory.
> 

I applied it, it just keeps mainstream files from including old hfs* files
in include/linux, but the old files stay around (you end with two
versions of hfs_fs.h, one in include/linux and other in fs/hfs...)
I did not move anything, just deleted those old files. But as other
filesystems put their xxxx_fs.h in include/linux, I thought that
perhaps hfs(plus) should do the same.

> > - I had to include linux/sched.h in hfs/sysdep.c to get the definition for
> >   'current', that was neded in some subinclude of linux/smp_lock. This can be
> >   caused by any other of my patches, but it doesn't hurt.
> 
> Simply move <linux/smp_lock.h> past "hfs_fs.h".
> 

Thanks.

-- 
J.A. Magallon <jamagallon()able!es>     \                 Software is like sex:
werewolf!able!es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.23-pre6-jam1 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk))


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-10-03 22:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02  8:37 [ANNOUNCE] new HFS(+) driver Roman Zippel
2003-10-02 18:02 ` Dave O
2003-10-02 18:30   ` Roman Zippel
2003-10-02 18:30     ` Roman Zippel
2003-10-02 19:00     ` Dave O
2003-10-02 19:00       ` Dave O
2003-10-03  0:26       ` Mike Fedyk
2003-10-03  2:43         ` Dave O
2003-10-03  2:43           ` Dave O
2003-10-02 18:06 ` viro
2003-10-02 18:24   ` Roman Zippel
2003-10-02 18:24     ` Roman Zippel
2003-10-02 18:52   ` Brad Boyer
2003-10-02 18:52     ` Brad Boyer
2003-10-06 19:38     ` Mike Fedyk
2003-10-06 19:38       ` Mike Fedyk
2003-10-06 19:47       ` Brad Boyer
2003-10-06 19:47         ` Brad Boyer
2003-10-03  7:04 ` J.A. Magallon
2003-10-03  7:04   ` J.A. Magallon
2003-10-03 10:30   ` Roman Zippel
2003-10-03 10:30     ` Roman Zippel
2003-10-03 22:39     ` J.A. Magallon [this message]
2003-10-03 22:39       ` J.A. Magallon
2003-10-04  3:00       ` Matthew Wilcox

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=20031003223904.GE30751@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hfsplus-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.