From: jay.p.patel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
Jay Patel <jay.p.patel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/1] Libibumad: Clarify the man page for function umad_get_ca_portguids
Date: Mon, 8 Aug 2016 13:49:57 -0400 [thread overview]
Message-ID: <1470678598-27218-1-git-send-email-jay.p.patel@intel.com> (raw)
From: Jay Patel <jay.p.patel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
The function umad_get_ca_portguids returns a value of 2 even if there is
only one valid port. The man page for the function only specifies that the
return value is equal to number of port GUIDs actually filled. This may be
confusing for user as it does not specify that there may be invalid entries
in the array.
Any change in interface may break existing user. Hence, clarification is
made in man page that some entries in the array may be invalid and should
be ignored.
Jay Patel (1):
Libibumad: Clarify the man page for function umad_get_ca_portguids
man/umad_get_ca_portguids.3 | 3 +++
1 file changed, 3 insertions(+)
--
1.8.2.3
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-08-08 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 17:49 jay.p.patel-ral2JQCrhuEAvxtiuMwx3w [this message]
[not found] ` <1470678598-27218-1-git-send-email-jay.p.patel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-08-08 17:49 ` [PATCH 1/1] Libibumad: Clarify the man page for function umad_get_ca_portguids jay.p.patel-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1470678598-27218-2-git-send-email-jay.p.patel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-08-08 21:49 ` Hal Rosenstock
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=1470678598-27218-1-git-send-email-jay.p.patel@intel.com \
--to=jay.p.patel-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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