From: Olaf Kirch <okir@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] NFS nolock broken in 2.6.9-rc4
Date: Mon, 18 Oct 2004 09:39:03 +0200 [thread overview]
Message-ID: <20041018073903.GB24684@suse.de> (raw)
In-Reply-To: <20041016004957.38ccd273.akpm@osdl.org>
On Sat, Oct 16, 2004 at 12:49:57AM -0700, Andrew Morton wrote:
> Did we come to a decision as to which patch to use?
>
> When we do, someone please send me the patch.
Trond's the one with the maintainer hat.
I like a separate file_operations_nolock better since it's KISS, but
if he prefers the long and winding road of locks.c calling NFS calling
locks.c, I'm fine with that, too.
Olaf
--
Olaf Kirch | Things that make Monday morning interesting, #1:
okir@suse.de | "I want to use NFS over AX25, can you help me?"
---------------+
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-10-18 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 9:58 [PATCH] NFS nolock broken in 2.6.9-rc4 Olaf Kirch
2004-10-15 10:07 ` Olaf Kirch
2004-10-15 14:46 ` Trond Myklebust
2004-10-15 15:11 ` Trond Myklebust
2004-10-15 15:13 ` Trond Myklebust
[not found] ` <20041016004957.38ccd273.akpm@osdl.org>
2004-10-18 7:39 ` Olaf Kirch [this message]
2004-10-15 14:44 ` Trond Myklebust
2004-10-15 15:12 ` Olaf Kirch
2004-10-15 15:21 ` Olaf Kirch
2004-10-15 16:47 ` Trond Myklebust
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=20041018073903.GB24684@suse.de \
--to=okir@suse.de \
--cc=akpm@osdl.org \
--cc=nfs@lists.sourceforge.net \
/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.