From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: Su Yue <glass.su@suse.com>
Cc: philipp.reisner@linbit.com, drbd-dev@lists.linbit.com
Subject: Re: [PATCH 2/2] crm-fence-peer.9.sh: use join of node_state to judge whether node is banned
Date: Wed, 17 Apr 2024 11:57:41 +0200 [thread overview]
Message-ID: <Zh+dFQrPLM6an2lk@grappa.linbit> (raw)
In-Reply-To: <48A9DD72-39A4-4866-B858-E50A33299CEB@suse.com>
On Thu, Mar 14, 2024 at 11:18:22AM +0800, Su Yue wrote:
>
>
> > On Mar 7, 2024, at 10:54, Su Yue <glass.su@suse.com> wrote:
> >
> > Hi, dear drbd folks
> > Would you help review the patches for drbd-utils? Many thanks!
> >
> Gentle ping.
So you apparently have some kind of test suite
excercising this fencing handler?
Thank you for making us aware, and for your patience.
Looks plausible.
Lars
next prev parent reply other threads:[~2024-04-17 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 9:12 [PATCH 1/2] crm-fence-peer.9.sh: fix parsing in_ccm crmd fields of node_state with Pacemaker 2.1.7 Su Yue
2024-03-03 9:12 ` [PATCH 2/2] crm-fence-peer.9.sh: use join of node_state to judge whether node is banned Su Yue
2024-03-07 2:54 ` Su Yue
2024-03-14 3:18 ` Su Yue
2024-04-17 9:57 ` Lars Ellenberg [this message]
2024-04-17 10:47 ` Glass Su
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=Zh+dFQrPLM6an2lk@grappa.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=glass.su@suse.com \
--cc=philipp.reisner@linbit.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