xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [PATCH 09/13] libxl: remove an unused numainfo parameter
Date: Thu, 2 Aug 2012 18:27:18 +0100	[thread overview]
Message-ID: <1343928442-23966-10-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1343928442-23966-1-git-send-email-ian.jackson@eu.citrix.com>

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Dario Faggioli <dario.faggioli@citrix.com>
---
 tools/libxl/libxl_numa.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/libxl/libxl_numa.c b/tools/libxl/libxl_numa.c
index 5301ec4..2c8e59f 100644
--- a/tools/libxl/libxl_numa.c
+++ b/tools/libxl/libxl_numa.c
@@ -231,7 +231,7 @@ static int nodemap_to_nr_vcpus(libxl__gc *gc, libxl_cputopology *tinfo,
  * candidates with just one node).
  */
 static int count_cpus_per_node(libxl_cputopology *tinfo, int nr_cpus,
-                               libxl_numainfo *ninfo, int nr_nodes)
+                               int nr_nodes)
 {
     int cpus_per_node = 0;
     int j, i;
@@ -340,7 +340,7 @@ int libxl__get_numa_candidate(libxl__gc *gc,
     if (!min_nodes) {
         int cpus_per_node;
 
-        cpus_per_node = count_cpus_per_node(tinfo, nr_cpus, ninfo, nr_nodes);
+        cpus_per_node = count_cpus_per_node(tinfo, nr_cpus, nr_nodes);
         if (cpus_per_node == 0)
             min_nodes = 1;
         else
-- 
1.7.2.5

  parent reply	other threads:[~2012-08-02 17:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 17:27 [PATCH v5 00/13] libxl: Assorted bugfixes and cleanups Ian Jackson
2012-08-02 17:27 ` [PATCH 01/13] libxl: unify libxl__device_destroy and device_hotplug_done Ian Jackson
2012-08-02 17:27 ` [PATCH 02/13] libxl: react correctly to bootloader pty master POLLHUP Ian Jackson
2012-08-03  8:32   ` Ian Campbell
2012-08-02 17:27 ` [PATCH 03/13] libxl: fix device counting race in libxl__devices_destroy Ian Jackson
2012-08-02 17:27 ` [PATCH 04/13] libxl: fix formatting of DEFINE_DEVICES_ADD Ian Jackson
2012-08-02 17:27 ` [PATCH 05/13] libxl: abolish useless `start' parameter to libxl__add_* Ian Jackson
2012-08-02 17:27 ` [PATCH 06/13] libxl: rename aodevs to multidev Ian Jackson
2012-08-02 17:27 ` [PATCH 07/13] libxl: do not blunder on if bootloader fails (again) Ian Jackson
2012-08-02 17:27 ` [PATCH 08/13] libxl: remus: mark TODOs more clearly Ian Jackson
2012-08-02 17:27 ` Ian Jackson [this message]
2012-08-02 17:27 ` [PATCH 10/13] libxl: idl: always initialise KeyedEnum keyvar in member init Ian Jackson
2012-08-02 17:27 ` [PATCH 11/13] libxl: correct some comments regarding event API and fds Ian Jackson
2012-08-03  8:35   ` Ian Campbell
2012-08-03 10:53     ` Ian Jackson
2012-08-02 17:27 ` [PATCH 12/13] libxl: add a comment re the memory management API instability Ian Jackson
2012-08-03  8:35   ` Ian Campbell
2012-08-02 17:27 ` [PATCH 13/13] libxl: -Wunused-parameter Ian Jackson
2012-08-03  8:08   ` Ian Campbell
2012-08-03  8:59 ` [PATCH v5 00/13] libxl: Assorted bugfixes and cleanups Ian Campbell
2012-08-03 11:05   ` Ian Jackson

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=1343928442-23966-10-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).