From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [ANNOUNCE] New rdma-core release available
Date: Tue, 21 Mar 2017 11:47:49 -0400 [thread overview]
Message-ID: <1490111269.2404.5.camel@redhat.com> (raw)
rdma-core version 13 has been released. This is the first release to
use the new release process (thanks to Leon for this). Among other
things, we should now have a properly formatted tarball on the release
page at github:
https://github.com/linux-rdma/rdma-core/releases/tag/v13
The properly formatted tarball shows up after a delay period (while
Travis CI does a test build and such). The old links for the release
that produce wonky tarballs are still there too. You'll want to use
the link that gives the tarball's name, not one of the links that says
"Source Code" if you want the properly formatted tarball.
Changes in this release are:
Minor improvements to qedr provider
Add libpvrdma provider for VMWare rdma virt devices
Improved RoCE AH creation
Packet Pacing support
Various github build system improvements
Updates to Debian and Red Hat packaging
Timestamp support in mlx4 provider
Make the libibverbs/provider interface private
Clean up headers for improved multi-arch support
Add Verbs Direct support for mlx5 provider
Implement new, more specific multi-arch barrier methods
Update all providers to the modern registration method and remove
ibv_register_driver entirely
Switch the code to use gcc endian conversion functions
Fix an endianness issue in srp_daemon
Implement a new release mechanism that should create more distro
friendly tarballs based on the common release tagging format
Updates to make it possible to run sparse on rdma-core
Fixes found by running sparse on rdma-core
Fixes to travis tarball upload script
Fix to broken cmake test
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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:[~2017-03-21 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 15:47 Doug Ledford [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-05 0:04 [ANNOUNCE] New rdma-core release available 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=1490111269.2404.5.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@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 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.