From: abeekhof@suse.de <abeekhof@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch 0/3] OCFS Configurable timeouts from userspace
Date: Fri Nov 17 23:36:39 2006 [thread overview]
Message-ID: <20061118073600.206222000@suse.de> (raw)
--
Jeff has asked me to finish off his configurable timeouts patch....
here's the results :-)
One thing I'm not so happy about are the changes (I made) to o2net_msg struct
in order to satisfy the logic in o2net_check_handshake()
Presumably the logic in o2net_check_handshake() should be changed?
Andrew
next reply other threads:[~2006-11-17 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 23:36 abeekhof [this message]
2006-11-17 23:36 ` [Ocfs2-devel] [patch 1/3] OCFS2 - Expose struct o2nm_cluster abeekhof
2006-11-17 23:36 ` [Ocfs2-devel] [patch 3/3] OCFS2 Configurable timeouts - Protocol changes abeekhof
2006-11-19 19:57 ` Mark Fasheh
2006-11-19 23:22 ` Andrew Beekhof
2006-11-20 9:38 ` Mark Fasheh
2006-11-20 10:13 ` Andrew Beekhof
2006-11-20 10:39 ` Zach Brown
2006-11-17 23:36 ` [Ocfs2-devel] [patch 2/3] OCFS2 Configurable timeouts abeekhof
2006-11-19 19:47 ` Mark Fasheh
2006-11-19 23:30 ` Andrew Beekhof
2006-11-20 9:39 ` Mark Fasheh
2006-11-18 2:35 ` [Ocfs2-devel] Re: [patch 0/3] OCFS Configurable timeouts from userspace Andrew Beekhof
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=20061118073600.206222000@suse.de \
--to=abeekhof@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
/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.