From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH/RFC] Replacing iget4/read_inode2 with icreate
Date: 01 May 2002 18:17:00 +0200 [thread overview]
Message-ID: <8O3bGfeHw-B@khms.westfalen.de> (raw)
In-Reply-To: <20020501024236.GA1878@mentor.odyssey.cs.cmu.edu>
jaharkes@cs.cmu.edu (Jan Harkes) wrote on 30.04.02 in <20020501024236.GA1878@mentor.odyssey.cs.cmu.edu>:
> +iget4() and the read_inode2 callback have been superceded by icreate()
> +which has the following prototype,
> +
> + struct inode *icreate(struct super_block *sb, unsigned long ino,
> + void (*test)(struct inode *, void *),
Surely test doesn't return a void?!
MfG Kai
prev parent reply other threads:[~2002-05-01 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 23:24 [PATCH/RFC] Replacing iget4/read_inode2 with icreate Jan Harkes
2002-04-30 6:12 ` Christoph Hellwig
2002-04-30 14:52 ` Jan Harkes
2002-04-30 15:50 ` Jan Harkes
2002-04-30 15:54 ` Steve Lord
2002-04-30 16:05 ` Steve Lord
2002-04-30 16:14 ` Jan Harkes
2002-04-30 16:29 ` Steve Lord
2002-04-30 16:40 ` Chris Mason
2002-04-30 17:03 ` Jan Harkes
2002-05-01 2:42 ` Jan Harkes
2002-05-01 3:25 ` Alexander Viro
2002-05-01 3:47 ` Jan Harkes
2002-05-01 16:17 ` Kai Henningsen [this message]
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=8O3bGfeHw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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