From: Filipe Brandenburger <filbranden@google.com>
To: linux-numa@vger.kernel.org
Cc: Cliff Wickman <cpw@sgi.com>, Petr Holasek <pholasek@redhat.com>
Subject: 2.0.11 release if libnuma/numactl
Date: Fri, 11 Dec 2015 07:47:59 -0800 [thread overview]
Message-ID: <CADU+-uAiHyHxbCpt-q_tU0fFtCPrTcd-biGbB==Vwa=zUHrgBg@mail.gmail.com> (raw)
The current version of libnuma and numactl is now released as 2.0.11.
The github repo has been tagged with v2.0.11:
https://github.com/numactl/numactl/releases/tag/v2.0.11
The latest tarball is available for download at:
ftp://oss.sgi.com/www/projects/libnuma/download/numactl-2.0.11.tar.gz
This version includes two new commits:
- 150116 libnuma: numa_node_to_cpu skips over non-existing nodes (Petr Holasek)
- 151210 libnuma: supress warnings for non-existing node (Petr Holasek)
Furthermore, the tarball for 2.0.11 was generated using `make dist`,
fixing the issue with the 2.0.10 tarball that did not include the
`configure` script and auxiliary file and required running
autoconf/automake.
Thanks!
Filipe
reply other threads:[~2015-12-11 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CADU+-uAiHyHxbCpt-q_tU0fFtCPrTcd-biGbB==Vwa=zUHrgBg@mail.gmail.com' \
--to=filbranden@google.com \
--cc=cpw@sgi.com \
--cc=linux-numa@vger.kernel.org \
--cc=pholasek@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).