mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH][2.6-mm] __kunmap/oprofile final link failure
Date: Sun, 23 Nov 2003 14:27:15 -0800	[thread overview]
Message-ID: <20031123142715.170109f5.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0311211811040.2498@montezuma.fsmlabs.com>

Zwane Mwaikambo <zwane@arm.linux.org.uk> wrote:
>
>  arch/i386/kernel/built-in.o(.text+0x927): In function `__switch_to':
>  arch/i386/kernel/process.c:564: undefined reference to 
>  `__kunmap_atomic_type'
>  arch/i386/kernel/built-in.o(.text+0x92e):arch/i386/kernel/process.c:565: 
>  undefined reference to `__kunmap_atomic_type'
>  arch/i386/kernel/built-in.o(.text+0x939):arch/i386/kernel/process.c:566: 
>  undefined reference to `__kmap_atomic'
>  arch/i386/kernel/built-in.o(.text+0x944):arch/i386/kernel/process.c:567: 
>  undefined reference to `__kmap_atomic'
>  arch/i386/kernel/built-in.o(.text+0x94e):arch/i386/kernel/process.c:572: 
>  undefined reference to `__kmap_atomic_vaddr'
>  arch/i386/oprofile/built-in.o(.text+0x171a): In function 
>  `oprofile_reset_stats':
>  include/asm/bitops.h:251: undefined reference to `cpu_possible_map'
>  arch/i386/oprofile/built-in.o(.text+0x179e): In function 
>  `oprofile_create_stats_files':
>  include/asm/bitops.h:251: undefined reference to `cpu_possible_map'
> 
>  Test compiled with NR_CPUS = 4, 64 and !CONFIG_SMP on i386

OK, there's just way too much compile breakage from the cpu_possible()
changes.  I'll drop them - something which does less reorganisation in the
headers is needed.


      reply	other threads:[~2003-11-23 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21 23:17 Zwane Mwaikambo
2003-11-23 22:27 ` Andrew Morton [this message]

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=20031123142715.170109f5.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zwane@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®