public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Don Dutile <ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Honggang Li <honli-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Announce: libibverbs-1.2.0
Date: Fri, 26 Feb 2016 12:01:23 -0500	[thread overview]
Message-ID: <56D084E3.7040207@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2301 bytes --]

I left libibverbs-1.2.0-rc1 out for quite a while.  I"ve went ahead and
made that the official libibverbs-1.2.0 (with only a few minor changes,
most notably just to correct some issues with the version string in the
tarball provided RPM spec file, and a fix for one compile warning).
This is mainly just preparatory for some of the recent patches on the
mailing list.  I felt those warranted a different version because of
their complexity.

However, the tarball isn't up yet.  I can't push it until I get a new
login on the new server at OpenFabrics.org (since that's been the
historical homes of the libibverbs tarballs, although it could be moved
to the tarball location on kernel.org in the future).  That request is
in and I'll update people on the list when I can push the tarball out.

The git repo has been pushed though, so if you grab the git repo, have a
recent set of autotools on your own machine, and then run "./autogen.sh;
make libibverbs.spec; make; make dist" then you should end up with a
tarball for libibverbs-1.2.0.tar.gz that is close enough to the official
one to allow you to check it out while waiting on the official one.

You might be asking yourself "Why is he announcing this if the tarball
isn't up?  Couldn't he just wait?"  And the answer to that is that I'm
currently working on libibverbs patches.  I don't frequently switch my
concentration and focus away from the kernel to libibverbs, so now is a
good time to get any minor patches in that you would like to see in
libibverbs-1.2.1 (the major patch sets are already on list, and I'm not
expecting people to push things like that through based on this notice,
but if someone wants to tackle little things like the fact that the XRC
version of example programs, which often support test that are not in
XRC mode, often don't check to see if inline data is supported and
therefore fail to run on qib cards...we expect it not to work on qib
cards when doing XRC tests since qib doesn't support XRC, but on non-XRC
tests is would be nice if they worked wherever possible).  Since I would
like to have a proposed libibverbs-1.2.1 ready to go by early next week,
I thought I would give people as much notice as possible instead of
waiting for the login to get finalized.

Thanks!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

             reply	other threads:[~2016-02-26 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 17:01 Doug Ledford [this message]
     [not found] ` <56D084E3.7040207-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-02 17:19   ` Announce: libibverbs-1.2.0 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=56D084E3.7040207@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=honli-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox