From: Olaf Kirch <olaf.kirch@oracle.com>
To: nfs@lists.sourceforge.net
Subject: Re: Oops in lockd (2.6.20.1)
Date: Mon, 5 Mar 2007 18:49:18 +0100 [thread overview]
Message-ID: <200703051849.18808.olaf.kirch@oracle.com> (raw)
In-Reply-To: <1173111509.6470.29.camel@heimdal.trondhjem.org>
On Monday 05 March 2007 17:18, Trond Myklebust wrote:
> Already fixed in 2.6.21-rc1 mainline.
Nice :)
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@lst.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-05 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 13:47 Oops in lockd (2.6.20.1) Jan Rekorajski
2007-03-05 15:36 ` Olaf Kirch
2007-03-05 16:18 ` Trond Myklebust
2007-03-05 17:49 ` Olaf Kirch [this message]
2007-03-05 17:54 ` Jan Rekorajski
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=200703051849.18808.olaf.kirch@oracle.com \
--to=olaf.kirch@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox