From: Miles Bader <miles@lsi.nec.co.jp>
To: Peter Braam <braam@clusterfs.com>
Cc: viro@math.psu.edu, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, lustre-devel@lists.sf.net
Subject: Re: [PATCH/RFC] 2.5 vfs intent lookup patch
Date: 25 Oct 2002 16:38:38 +0900 [thread overview]
Message-ID: <buohefbge81.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20021025063249.GA1359@localhost.localdomain>
Peter Braam <braam@clusterfs.com> writes:
> Attached is a 2.5 patch for lookup intents, which we use with Lustre.
> This patch adds a lookup2, revalidate2 and intent_release method.
>
> Do you have a good idea how to do this better?
At least use better names than `lookup2' &c.
[`lookup_with_intent'?]
-Miles
--
Somebody has to do something, and it's just incredibly pathetic that it
has to be us. -- Jerry Garcia
prev parent reply other threads:[~2002-10-25 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 6:32 [PATCH/RFC] 2.5 vfs intent lookup patch Peter Braam
2002-10-25 7:38 ` Miles Bader [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=buohefbge81.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=braam@clusterfs.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.sf.net \
--cc=miles@gnu.org \
--cc=viro@math.psu.edu \
/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