From: jbarnes@sgi.com (Jesse Barnes)
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make lookup_create non-static
Date: Mon, 4 Aug 2003 15:30:38 -0700 [thread overview]
Message-ID: <20030804223037.GA2214@sgi.com> (raw)
In-Reply-To: <20030804145723.533e77f7.akpm@osdl.org>
On Mon, Aug 04, 2003 at 02:57:23PM -0700, Andrew Morton wrote:
> jbarnes@sgi.com (Jesse Barnes) wrote:
> >
> > You mean copy lookup_create into hwgfs (which is already in the tree,
> > btw)? Yeah, I guess I could do that if you don't want to take this.
>
> ah, I thought you were referring to an out-of-tree filesystem.
>
> It would appear that intermezzo has already created a private copy of
> lookup_create(). Sigh.
>
> If we're going to export this thing to filesystems then it really should be
> documented a bit. You could bribe me with a patch which does that ;)
Ok, how does this look?
Jesse
===== fs/namei.c 1.81 vs edited =====
--- 1.81/fs/namei.c Thu Jul 10 22:23:45 2003
+++ edited/fs/namei.c Mon Aug 4 15:28:38 2003
@@ -1375,8 +1375,15 @@
goto do_last;
}
-/* SMP-safe */
-static struct dentry *lookup_create(struct nameidata *nd, int is_dir)
+/**
+ * lookup_create - lookup a dentry, creating it if it doesn't exist
+ * @nd: nameidata info
+ * @is_dir: directory flag
+ *
+ * Simple function to lookup and return a dentry and create it
+ * if it doesn't exist. Is SMP-safe.
+ */
+struct dentry *lookup_create(struct nameidata *nd, int is_dir)
{
struct dentry *dentry;
next prev parent reply other threads:[~2003-08-04 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 21:35 [PATCH] make lookup_create non-static Jesse Barnes
2003-08-04 21:41 ` Andrew Morton
2003-08-04 21:44 ` Jesse Barnes
2003-08-04 21:57 ` Andrew Morton
2003-08-04 22:30 ` Jesse Barnes [this message]
2003-08-04 22:39 ` Andrew Morton
2003-08-04 22:40 ` Jesse Barnes
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=20030804223037.GA2214@sgi.com \
--to=jbarnes@sgi.com \
--cc=akpm@osdl.org \
--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 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.