From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/2] fence_scsi: fix typos in debug messages
Date: Wed, 18 Apr 2012 05:54:17 +0200 [thread overview]
Message-ID: <4F8E3AE9.4050800@redhat.com> (raw)
In-Reply-To: <4F8E0472.6080700@redhat.com>
ACK
On 04/18/2012 02:01 AM, Ryan O'Hara wrote:
> Resolves: rhbz#674497
>
> Signed-off-by: Ryan O'Hara <rohara@redhat.com>
> ---
> fence/agents/scsi/fence_scsi.pl | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fence/agents/scsi/fence_scsi.pl
> b/fence/agents/scsi/fence_scsi.pl
> index 91f113d..84cee91 100755
> --- a/fence/agents/scsi/fence_scsi.pl
> +++ b/fence/agents/scsi/fence_scsi.pl
> @@ -111,7 +111,7 @@ sub get_node_id
> sub get_node_name
> {
> - print "[$pname]: get_hode_name = $opt_n\n" if $opt_v;
> + print "[$pname]: get_node_name = $opt_n\n" if $opt_v;
> return $opt_n;
> }
> @@ -163,7 +163,7 @@ sub get_host_name
> }
> }
> - print "[$pname]: get_host_nam = $host_name\n" if $opt_v;
> + print "[$pname]: get_host_name = $host_name\n" if $opt_v;
> return $host_name;
> }
prev parent reply other threads:[~2012-04-18 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 0:01 [Cluster-devel] [PATCH 1/2] fence_scsi: fix typos in debug messages Ryan O'Hara
2012-04-18 3:54 ` Fabio M. Di Nitto [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=4F8E3AE9.4050800@redhat.com \
--to=fdinitto@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 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).