From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Shantanu Goel" <Shantanu.Goel@lehman.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename]
Date: Fri, 28 Nov 2003 12:05:15 -0500 [thread overview]
Message-ID: <16327.32843.197191.606592@charged.uio.no> (raw)
In-Reply-To: <3FC77CC3.7090702@lehman.com>
>>>>> " " == Shantanu Goel <Shantanu.Goel@lehman.com> writes:
> BTW, this also affects 2.4 kernels (e.g. RedHat's AS3 kernel)
> which include your CTO patches that aren't in the upstream
> kernels yet.
AFAIK Steve Dickson is already aware of the need for this particular
patch for the AS3 kernel. He was one of the people that brought it to
my attention a couple of weeks ago.
Cheers,
Trond
prev parent reply other threads:[~2003-11-28 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 15:03 [Fwd: [NFS PATCH] 2.6.0-test10 Invalidate cached inode attributes after rename] Shantanu Goel
2003-11-28 16:45 ` Trond Myklebust
2003-11-28 16:50 ` Shantanu Goel
2003-11-28 17:05 ` Trond Myklebust [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=16327.32843.197191.606592@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Shantanu.Goel@lehman.com \
--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;
as well as URLs for NNTP newsgroup(s).