public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
To: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ANNOUNCE] libibmad 1.3.9 release
Date: Thu, 31 May 2012 17:25:58 -0700	[thread overview]
Message-ID: <20120531172558.8c11c4cf.weiny2@llnl.gov> (raw)
In-Reply-To: <20120531165945.fecda3c7.weiny2-i2BcT+NCU+M@public.gmane.org>

On Thu, 31 May 2012 16:59:45 -0700
Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org> wrote:

> There is a new release of libibmad.
> 
> Tarball available at:[*]

I have managed to fix this problem.  I was confused on the server change.  libibmad is now available at:

http://downloads.openfabrics.org/management/libibmad-1.3.9.tar.gz
or
https://www.openfabrics.org/downloads/management/libibmad-1.3.9.tar.gz

Sorry,
Ira

> http://sofa.openfabrics.org/downloads/management/libibmad-1.3.9.tar.gz
> 
> 5bff1406b95d6165ae31acc9f01482e0  libibmad-1.3.9.tar.gz
> 
> Dependencies:
> 
> 	1) libibumad >= 1.3.7
> 	2) opensm-libs >= 3.3.10
> 	3) ib_umad kernel module
> 
> Release notes for 1.3.8 to 1.3.9 are:
> 
>    1) bug fixes
>    2) Add support for Congestion Control MAD's
>    3) Add SA NodeRecord
>    4) Add MKey support to ibmad_port object
>    5) Update counter offsets for PortExtendedSpeedsCounters
>    6) Additional print functions
>         classportinfo dump function
> 	additional debugging
> 
>    These changes increment the soname to 8 but the library is backwards
>    compatible to soname 5.
> 
> 
> Git log
> =======
> 
> Author: Jim Foraker <foraker1-i2BcT+NCU+M@public.gmane.org>
> 
>     libibmad/dump.c: clean up boundary conditions in dump routines
>     libibmad: Add MKey support to SMP requests via smp_mkey_get/set()
> 
> Author: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
> 
>     libibmad/fields.c: Update counter offsets for PortExtendedSpeedsCounters
>     libibmad: Add support for SA NodeRecord
>     libibmad/rpc.c: On receive, add debug info for dumping incoming MAD address
> 
> Author: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
> 
>     libibmad: fix misspelling
>     libibmad: Add support for congestion control config mads.
>     Support classportinfo dump function
>     Add support for congestion control mads
> 
> 
> [*] I am not sure why the tarball does not appear on www.openfabrics.org/downloads or downloads.openfabrics.org.
> 
> -- 
> Ira Weiny
> Member of Technical Staff
> Lawrence Livermore National Lab
> 925-423-8008
> weiny2-i2BcT+NCU+M@public.gmane.org


-- 
Ira Weiny
Member of Technical Staff
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org
--
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

      parent reply	other threads:[~2012-06-01  0:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 23:59 [ANNOUNCE] libibmad 1.3.9 release Ira Weiny
     [not found] ` <20120531165945.fecda3c7.weiny2-i2BcT+NCU+M@public.gmane.org>
2012-06-01  0:25   ` Ira Weiny [this message]

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=20120531172558.8c11c4cf.weiny2@llnl.gov \
    --to=weiny2-i2bct+ncu+m@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