mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-hfsplus-devel@lists.sourceforge.net,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] new HFS(+) driver
Date: Fri, 3 Oct 2003 12:30:36 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0310031227460.17548-100000@serv> (raw)
In-Reply-To: <20031003070422.GA8627@werewolf.able.es>

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 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".

bye, Roman


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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02  8:37 Roman Zippel
2003-10-02 18:02 ` Dave O
2003-10-02 18:30   ` Roman Zippel
2003-10-02 19:00     ` Dave O
2003-10-03  0:26       ` Mike Fedyk
2003-10-03  2:43         ` Dave O
2003-10-02 18:06 ` viro
2003-10-02 18:24   ` Roman Zippel
2003-10-02 18:52   ` Brad Boyer
2003-10-06 19:38     ` Mike Fedyk
2003-10-06 19:47       ` Brad Boyer
2003-10-03  7:04 ` J.A. Magallon
2003-10-03 10:30   ` Roman Zippel [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=Pine.LNX.4.44.0310031227460.17548-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=jamagallon@able.es \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hfsplus-devel@lists.sourceforge.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®