public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Williams <dsw@gelato.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: [patch] fix HP simulator smp build replace __devinit -> __initdata
Date: Mon, 09 May 2005 06:57:11 +0000	[thread overview]
Message-ID: <20050509065711.GI5692@cse.unsw.EDU.AU> (raw)

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

Since we have updated the Autobuild system to use Cogito
we can start to report and submit patches on the latest
check-ins that break the build. 

Currently on the Gelato@UNSW Autobuild system:
http://www.gelato.unsw.edu.au/kerncomp/
we are seeing the sim_defconfig build fail, with the
following error:

arch/ia64/kernel/smpboot.c:627: error: mt_info causes a section type conflict

the following non-git patch fixes the problem, tested
on simulator, and zx1. I'm not sure why the simulator
is triggering this build failure since zx1 sn2 are
building OK?

 - dsw

--------------------------------------------------
Darren Williams <dsw AT gelato.unsw.edu.au>
Gelato@UNSW <www.gelato.unsw.edu.au>
--------------------------------------------------

[-- Attachment #2: smpboot.patch --]
[-- Type: text/plain, Size: 377 bytes --]

--- linux-2.6-orig/arch/ia64/kernel/smpboot.c	2005-05-09 16:25:09.000000000 +1000
+++ linux-2.6-import/arch/ia64/kernel/smpboot.c	2005-05-09 15:53:15.000000000 +1000
@@ -624,7 +624,7 @@ static struct {
 	__u16   thread_id;
 	__u16   proc_fixed_addr;
 	__u8    valid;
-}mt_info[NR_CPUS] __devinit;
+}mt_info[NR_CPUS] __initdata;
 
 #ifdef CONFIG_HOTPLUG_CPU
 static inline void

             reply	other threads:[~2005-05-09  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09  6:57 Darren Williams [this message]
2005-05-09  7:24 ` [patch] fix HP simulator smp build replace __devinit -> __initdata Keith Owens
2005-05-09 11:21 ` [patch] fix HP simulator smp build replace __devinit -> __devinitdata (revised) Darren Williams

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=20050509065711.GI5692@cse.unsw.EDU.AU \
    --to=dsw@gelato.unsw.edu.au \
    --cc=linux-ia64@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