From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] RFC: Drop support for libnuma API version < 2
Date: Mon, 28 Aug 2017 07:54:52 -0400 (EDT) [thread overview]
Message-ID: <367492676.4269530.1503921292583.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170828083904.4kc7ndp2jdwugs7f@dell5510>
----- Original Message -----
> Hi,
>
> I'm just about to rewrite mbind/mbind01 test to new API. This test (and some
> other tests)
> still support libnuma API version < 2. Libnuma version 2 was released in
> 2008. Do we still want
> to support older versions?
Hi,
I would go with "no" for writing new code against libnuma < 2. Looking at
LTP, I see only handful of tests that have specific code for old (< 2)
libnuma.
But I'd like to keep LTP compilable with these old distros,
since there are lot of tests that still can be used.
Regards,
Jan
next prev parent reply other threads:[~2017-08-28 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 8:39 [LTP] RFC: Drop support for libnuma API version < 2 Petr Vorel
2017-08-28 11:54 ` Jan Stancek [this message]
2017-08-28 12:24 ` Petr Vorel
2017-08-28 12:30 ` Jan Stancek
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=367492676.4269530.1503921292583.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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