From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [Patch libibverbs 0/5] Minor updates
Date: Sun, 14 Oct 2012 13:02:58 -0400 [thread overview]
Message-ID: <cover.1350234101.git.dledford@redhat.com> (raw)
This is a short series of fixes for minor issues. The most important
being a memcpy buffer overrun on ppc arch for the compatibility wrapper.
The rest are usability fixes for the example programs.
Doug Ledford (5):
Add an error when the user specifies an invalid port
Don't allow port == 0 as an option
Fix the compatibility wrapper on ppc
Don't print link phys state on iWARP
Don't try to send UD messages larger than MTU
examples/devinfo.c | 15 +++++++++++----
examples/ud_pingpong.c | 14 ++++++++++++++
src/compat-1_0.c | 42 ++++++++++++++++++++++++++++++++++++++++--
3 files changed, 65 insertions(+), 6 deletions(-)
--
1.7.7.6
--
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:[~2012-10-14 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 17:02 Doug Ledford [this message]
[not found] ` <cover.1350234101.git.dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-10-14 17:02 ` [Patch libibverbs 1/5] Add an error when the user specifies an invalid port Doug Ledford
2012-10-14 17:03 ` [Patch libibverbs 2/5] Don't allow port == 0 as an option Doug Ledford
2012-10-14 17:03 ` [Patch libibverbs 3/5] Fix the compatibility wrapper on ppc Doug Ledford
2012-10-14 17:03 ` [Patch libibverbs 4/5] Don't print link phys state on iWARP Doug Ledford
2012-10-14 17:03 ` [Patch libibverbs 5/5] Don't try to send UD messages larger than MTU Doug Ledford
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=cover.1350234101.git.dledford@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@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;
as well as URLs for NNTP newsgroup(s).