From: Eric Ren <zren@suse.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [DLM PATCH] dlm_controld: add option of enable_force_kick
Date: Tue, 17 May 2016 20:16:36 +0800 [thread overview]
Message-ID: <573B0BA4.8020306@suse.com> (raw)
In-Reply-To: <20160516171254.GC20979@redhat.com>
Hello David:
On 05/17/2016 01:12 AM, David Teigland wrote:
> This looks good. Would you still use this patch if we add the new
> dlm_tool output from the other email?
Please hold back this for now;-) I prefer to drop this method if the
latter one works better. And I'm trying to working this out with
pacemaker guys;-)
Thanks a lot,
Eric
prev parent reply other threads:[~2016-05-17 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 8:07 [Cluster-devel] [DLM PATCH] dlm_controld: add option of enable_force_kick Eric Ren
2016-05-16 17:12 ` David Teigland
2016-05-17 12:16 ` Eric Ren [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=573B0BA4.8020306@suse.com \
--to=zren@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).