All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] fence_xvm: Fix incorrect success return codes
Date: Wed, 25 Jul 2012 10:50:28 -0400	[thread overview]
Message-ID: <501007B4.6080705@redhat.com> (raw)
In-Reply-To: <20120725144331.GA71022@redhat.com>

On 07/25/2012 10:43 AM, Ryan McCabe wrote:
> This patch fixes two places where fence_xvm will return success
> for fencing operations when fencing has failed due to the
> challenge/response failing.

Resolves: rhbz#843083

ACK.

-- Lon



      reply	other threads:[~2012-07-25 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 14:43 [Cluster-devel] [PATCH] fence_xvm: Fix incorrect success return codes Ryan McCabe
2012-07-25 14:50 ` Lon Hohberger [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=501007B4.6080705@redhat.com \
    --to=lhh@redhat.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.