From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Jeff L. Smith" <jeff@atheros.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: Vaguely NFS related problem
Date: 13 Dec 2002 15:07:10 +0100 [thread overview]
Message-ID: <shs65ty9fn5.fsf@charged.uio.no> (raw)
In-Reply-To: <3DF8C2BF.8050109@atheros.com>
>>>>> " " == Jeff L Smith <jeff@atheros.com> writes:
> I plan to upgrade to 2.4.20 as soon as I can take the
> fileservers down long enough, but that will be a few weeks.
> But then that begs the question, should I apply Trond's 2.4.20
> patches?
FYI: There are no further NFS server-related patches in my 2.4.20
patchsets.
The only server patches I included earlier were beta-versions of the
NFS over TCP related stuff ('cos they conflicted with some of the
client changes). Now that the finalized TCP code has been merged into
the mainstream kernel by Neil, I've dropped them.
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-12-13 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 1:47 Vaguely NFS related problem Jeff L. Smith
2002-12-12 2:12 ` Neil Brown
2002-12-12 2:37 ` Jeff L. Smith
2002-12-12 3:00 ` Neil Brown
2002-12-12 17:09 ` Jeff L. Smith
2002-12-13 14:07 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 2:41 Jeff L. Smith
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=shs65ty9fn5.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=jeff@atheros.com \
--cc=neilb@cse.unsw.edu.au \
--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.