public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Malte Schröder" <MalteSch@gmx.de>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with nfs4, kernel 2.6.13.2
Date: Mon, 10 Oct 2005 21:33:21 +0200	[thread overview]
Message-ID: <434AC201.7050904@gmx.de> (raw)
In-Reply-To: <1128957945.8451.19.camel@lade.trondhjem.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trond Myklebust wrote:
> su den 09.10.2005 Klokka 22:57 (+0200) skreiv Malte Schröder:
> 
>>>>>You may also want to retest with
>>>>>
>>>>>http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.13-1/linux-2.6.13-001-NFS_ALL_MODIFIED.dif
>>>>>
> I wrote all the elements in that patch so believe me, it has been
> considered. 8-)
> 
> ...however I still need to clean a few things up a bit before I'm ready
> to send it on to Andrew and Linus. Do not expect it to appear in 2.6.14,
> but rather in 2.6.15 (and possibly the 2.6.14-mm).

I have been doing some testing of 2.6.13.2 with that patch applied on
two different machines and it seems to be working :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDSsIB4q3E2oMjYtURAo3pAKC7+iJ8LHhV2DuOon4WxyxUtI4+UQCeNkgh
1OZUcL9q1mmSU8Xj/h2cJJc=
=s5O2
-----END PGP SIGNATURE-----

      reply	other threads:[~2005-10-10 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-25 13:16 Problem with nfs4, kernel 2.6.13.2 Malte Schröder
2005-09-26 12:28 ` Trond Myklebust
2005-09-26 14:21   ` Malte Schröder
2005-09-26 20:18   ` Malte Schröder
2005-10-09 20:57     ` Malte Schröder
2005-10-10 15:25       ` Trond Myklebust
2005-10-10 19:33         ` Malte Schröder [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=434AC201.7050904@gmx.de \
    --to=maltesch@gmx.de \
    --cc=Trond.Myklebust@netapp.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