All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Wei Gao via ltp" <ltp@lists.linux.it>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] set_mempolicy: require CONFIG_NUMA
Date: Tue, 30 Jun 2026 11:10:15 +0000	[thread overview]
Message-ID: <6a43a418.da15fda7.276e06.e569@mx.google.com> (raw)
In-Reply-To: <aj6Iml1fSH2IwjqN@autotest-wegao.qe.prg2.suse.org>

Hi Wei,

> I suppose we do not need "#ifdef HAVE_NUMA_V2" anymore in the code.
> Same for set_mempolicy02 etc

HAVE_NUMA_V2 is used to check if NUMA is available at user-space via
libnuma or during LTP build via --with-numa option, so we need to keep it.

The patch is LGTM and we are ready to merge it.

Reviewed-by: Andrea Cervesato <andrea.cervesato@suse.com>

--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-06-30 11:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 12:48 [LTP] [PATCH] set_mempolicy05: require CONFIG_NUMA Avinesh Kumar via ltp
2026-06-23 15:51 ` [LTP] " linuxtestproject.agent
2026-06-24  8:14 ` [LTP] [PATCH] " Andrea Cervesato via ltp
2026-06-24 15:41   ` Avinesh Kumar via ltp
2026-06-25  7:01     ` Andrea Cervesato via ltp
2026-06-25 14:57       ` [LTP] [PATCH v2] set_mempolicy: " Avinesh Kumar via ltp
2026-06-26  9:13         ` Andrea Cervesato via ltp
2026-06-26 13:53           ` [LTP] [PATCH v3] " Avinesh Kumar via ltp
2026-06-26 14:11             ` Wei Gao via ltp
2026-06-30 11:10               ` Andrea Cervesato via ltp [this message]
2026-06-30  9:22             ` [LTP] " linuxtestproject.agent
2026-06-30 11:17             ` [LTP] [PATCH v3] " Andrea Cervesato via ltp

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=6a43a418.da15fda7.276e06.e569@mx.google.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.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 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.