All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-04-28-16-53 uploaded
Date: Fri, 30 Apr 2010 14:47:49 -0400	[thread overview]
Message-ID: <21637.1272653269@localhost> (raw)
In-Reply-To: Your message of "Fri, 30 Apr 2010 14:02:27 EDT." <1272650547.10027.97.camel@useless.americas.hpqcorp.net>

[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]

On Fri, 30 Apr 2010 14:02:27 EDT, Lee Schermerhorn said:

> Would you have time to try a few patches?  I've been doing some rework
> of the generic percpu numa_node/numa_mem patches.  This rework should
> solve the build problem you encountered.

Not sure if I bollixed up adding the patches to the series file, that
section now looks like:

% grep -n ^numa series
1465:numa-add-generic-percpu-var-numa_node_id-implementation.patch
1466:numa-add-generic-percpu-var-numa_node_id-implementation-fix1.patch
1467:numa-add-generic-percpu-var-numa_node_id-implementation-fix2.patch
1468:numa-x86_64-use-generic-percpu-var-numa_node_id-implementation.patch
1469:numa-x86_64-use-generic-percpu-var-numa_node_id-implementation-fix1.patch
1470:numa-x86_64-use-generic-percpu-var-numa_node_id-implementation-fix2.patch
1471:numa-ia64-use-generic-percpu-var-numa_node_id-implementation.patch
1473:numa-introduce-numa_mem_id-effective-local-memory-node-id.patch
1474:numa-introduce-numa_mem_id-effective-local-memory-node-id-fix.patch
1475:numa-introduce-numa_mem_id-effective-local-memory-node-id-fix2.patch
1476:numa-introduce-numa_mem_id-effective-local-memory-node-id-fix3.patch
1477:numa-ia64-support-numa_mem_id-for-memoryless-nodes.patch
1478:numa-slab-use-numa_mem_id-for-slab-local-memory-node.patch
1479:numa-in-kernel-profiling-use-cpu_to_mem-for-per-cpu-allocations.patch
1480:numa-update-documentation-vm-numa-add-memoryless-node-info.patch
1481:numa-update-documentation-vm-numa-add-memoryless-node-info-fix1.patch

and it dies with:

 LANG=C make
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CC      arch/x86/kernel/asm-offsets.s
In file included from include/linux/gfp.h:7,
                 from include/linux/kmod.h:22,
                 from include/linux/module.h:13,
                 from include/linux/crypto.h:21,
                 from arch/x86/kernel/asm-offsets_64.c:8,
                 from arch/x86/kernel/asm-offsets.c:4:
include/linux/topology.h:246: error: redefinition of 'numa_node_id'
/usr/src/linux-2.6.34-rc5-mmotm0428/arch/x86/include/asm/topology.h:163: note: previous definition of 'numa_node_id' was here
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2

X86_64 build, CONFIG_NUMA=n - looks like include/linux/topology.h doesn't
play nice in the !CONFIG_USE_PERCPU_NUMA_NODE_ID case...


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2010-04-30 18:49 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 23:53 mmotm 2010-04-28-16-53 uploaded akpm
2010-04-29 21:32 ` Valdis.Kletnieks
2010-04-29 21:53   ` Andrew Morton
2010-04-29 22:00     ` Andrew Morton
2010-04-30 12:11       ` Lee Schermerhorn
2010-04-30 18:02   ` Lee Schermerhorn
2010-04-30 18:47     ` Valdis.Kletnieks [this message]
2010-04-30 19:05       ` Lee Schermerhorn
2010-05-02 17:38 ` mmotm 2010-04-28 - nouveau driver issues Valdis.Kletnieks
2010-05-02 17:38 ` Valdis.Kletnieks
2010-05-02 17:46 ` mmotm 2010-04-28 - RCU whinges Valdis.Kletnieks
2010-05-03  5:38   ` Eric Dumazet
2010-05-03  5:41     ` Eric Dumazet
2010-05-03  5:41       ` Eric Dumazet
2010-05-03  5:43       ` Eric Dumazet
2010-05-03  5:43         ` Eric Dumazet
2010-05-03  5:55         ` David Miller
2010-05-10 15:40           ` Patrick McHardy
2010-05-10 15:56             ` Eric Dumazet
2010-05-10 15:57               ` Eric Dumazet
2010-05-10 16:03               ` Patrick McHardy
2010-05-10 16:03                 ` Patrick McHardy
2010-05-10 16:04                 ` Patrick McHardy
2010-05-10 16:04                   ` Patrick McHardy
2010-05-10 15:57             ` Paul E. McKenney
2010-05-10 16:12             ` David Miller
2010-05-10 16:27               ` Patrick McHardy
2010-05-03 14:30     ` Valdis.Kletnieks
2010-05-03 14:48       ` Eric Dumazet
2010-05-03 14:48         ` Eric Dumazet
2010-05-03 14:58       ` Eric Dumazet
2010-05-03 15:29         ` Valdis.Kletnieks
2010-05-03 15:43           ` Paul E. McKenney
2010-05-03 15:43             ` Paul E. McKenney
2010-05-03 16:14             ` Eric Dumazet
2010-05-03 18:16               ` Paul E. McKenney
2010-05-03 18:16                 ` Paul E. McKenney
2010-05-03 19:46                 ` [PATCH net-next-2.6] net: if6_get_next() fix Eric Dumazet
2010-05-03 20:09                   ` David Miller
2010-05-03 20:13                     ` Eric Dumazet
2010-05-03 20:13                       ` Eric Dumazet
2010-05-03 20:24                       ` David Miller
2010-05-03 20:50                         ` Eric Dumazet
2010-05-03 22:17                           ` David Miller
2010-05-03 22:48                             ` Paul E. McKenney
2010-05-03 22:52                           ` Paul E. McKenney
2010-05-03 22:54                             ` David Miller
2010-05-10 16:53     ` mmotm 2010-04-28 - RCU whinges Patrick McHardy

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=21637.1272653269@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 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.