public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc2-mm2
Date: Fri, 8 Apr 2005 13:46:58 +0200	[thread overview]
Message-ID: <200504081346.59282.rjw@sisk.pl> (raw)
In-Reply-To: <20050408030835.4941cd98.akpm@osdl.org>

On Friday, 8 of April 2005 12:08, Andrew Morton wrote:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm2/
> 
> 
> - Although small, bk-audit.patch was causing conflits with a couple of
>   other projects.  Dropped for now.
> 
> - Greg is not using bk now, so bk-pci.patch, bk-i2c.patch,
>   bk-driver-core.patch and bk-usb.patch have been replaced with gregkh-*.patch
>   in -mm.
> 
> - Largeish x86_64 update

It does not compile on a uniprocessor x86-64:

  CC      arch/x86_64/kernel/process.o
  CC      arch/x86_64/kernel/semaphore.o
  CC      arch/x86_64/kernel/signal.o
  AS      arch/x86_64/kernel/entry.o
  CC      arch/x86_64/kernel/traps.o
  CC      arch/x86_64/kernel/irq.o
  CC      arch/x86_64/kernel/ptrace.o
  CC      arch/x86_64/kernel/time.o
  CC      arch/x86_64/kernel/ioport.o
  CC      arch/x86_64/kernel/ldt.o
  CC      arch/x86_64/kernel/setup.o
arch/x86_64/kernel/setup.c: In function `amd_detect_cmp':
arch/x86_64/kernel/setup.c:759: error: `cpu_core_id' undeclared (first use in this function)
arch/x86_64/kernel/setup.c:759: error: (Each undeclared identifier is reported only once
arch/x86_64/kernel/setup.c:759: error: for each function it appears in.)
make[1]: *** [arch/x86_64/kernel/setup.o] Error 1
make: *** [arch/x86_64/kernel] Error 2

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-04-08 11:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 10:08 2.6.12-rc2-mm2 Andrew Morton
2005-04-08 11:46 ` Rafael J. Wysocki [this message]
2005-04-08 16:44   ` 2.6.12-rc2-mm2 Rafael J. Wysocki
2005-04-08 12:25 ` 2.6.12-rc2-mm2 Indrek Kruusa
2005-04-08 14:11 ` 2.6.12-rc2-mm2 Jan Dittmer
2005-04-08 15:23   ` 2.6.12-rc2-mm2 Paulo Marques
2005-04-08 14:14 ` 2.6.12-rc2-mm2 Jan Dittmer
2005-04-08 22:21   ` 2.6.12-rc2-mm2 Andrew Morton
2005-04-08 15:17 ` 2.6.12-rc2-mm2 Alexander Nyberg
2005-04-08 17:28 ` 2.6.12-rc2-mm2 Alexey Dobriyan
2005-04-08 13:52   ` 2.6.12-rc2-mm2 Martin Waitz
2005-04-08 23:28 ` 2.6.12-rc2-mm2 Jesper Juhl
2005-04-09  1:49   ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-09  1:57     ` 2.6.12-rc2-mm2 Jesper Juhl
2005-04-09 12:51       ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-09 13:43 ` 2.6.12-rc2-mm2 Alexander Nyberg
2005-04-10 13:31 ` 2.6.12-rc2-mm2 Alexander Nyberg
2005-04-10 22:48 ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-11 15:18   ` 2.6.12-rc2-mm2 Paul E. McKenney
2005-04-13  0:36     ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-13  1:32       ` 2.6.12-rc2-mm2 Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2005-04-08 11:50 2.6.12-rc2-mm2 Michael Thonke
2005-04-10 15:06 2.6.12-rc2-mm2 Pavel Machek

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=200504081346.59282.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox