From: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Gris Ge <fge@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: [PATCH] multipath-tools: fix errors in auto generated man pages
Date: Mon, 12 Mar 2018 21:52:43 +0100 [thread overview]
Message-ID: <20180312205243.10892-1-xose.vazquez@gmail.com> (raw)
dmmp_path_blk_name_get.3:
<standard input>:14: warning: macro `nvme0n1'.' not defined
dmmp_mpath_kdev_name_get.3:
<standard input>:15: warning: macro `dm-1'.' not defined
Cc: Gris Ge <fge@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
---
libdmmp/libdmmp/libdmmp.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/libdmmp/libdmmp/libdmmp.h b/libdmmp/libdmmp/libdmmp.h
index e157982..6e6610d 100644
--- a/libdmmp/libdmmp/libdmmp.h
+++ b/libdmmp/libdmmp/libdmmp.h
@@ -389,7 +389,7 @@ DMMP_DLL_EXPORT const char *dmmp_mpath_name_get(struct dmmp_mpath *dmmp_mp);
* dmmp_mpath_kdev_name_get() - Retrieve kernel DEVNAME of certain mpath.
*
* Retrieve DEVNAME name used by kernel uevent of specified mpath.
- * Example: 'dm-1'.
+ * For example: 'dm-1'.
*
* @dmmp_mp:
* Pointer of 'struct dmmp_mpath'.
@@ -553,8 +553,8 @@ DMMP_DLL_EXPORT void dmmp_path_array_get(struct dmmp_path_group *dmmp_pg,
/**
* dmmp_path_blk_name_get() - Retrieve block name.
*
- * Retrieve block name of certain path. The example of block names are 'sda',
- * 'nvme0n1'.
+ * Retrieve block name of certain path. The example of block names are "sda",
+ * "nvme0n1".
*
* @dmmp_p:
* Pointer of 'struct dmmp_path'.
--
2.14.3
reply other threads:[~2018-03-12 20:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180312205243.10892-1-xose.vazquez@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=dm-devel@redhat.com \
--cc=fge@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