public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: adobriyan@gmail.com, Arnd Bergmann <arnd@arndb.de>,
	oberpar@linux.vnet.ibm.com,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	John Williams <john.williams@petalogix.com>
Subject: [GIT PULL] arch/microblaze bug-fix for merge window (2.6.31)
Date: Sat, 20 Jun 2009 14:58:38 +0200	[thread overview]
Message-ID: <4A3CDCFE.9080200@monstr.eu> (raw)

Hi Linus,

these two patches solve compilation build failures because
Alexey Dobriyan (bb1f17b0372de93758653ca3454bc0df18dc2e5c) forget to
remove init_mm from Microblaze kernel code.

and

Peter Oberparleiter (b99b87f70c7785ab1e253c6220f4b0b57ce3a7f7) add
constructor support
and Microblaze hadn't some exported symbols

Please add them asap.

Thanks,
Michal


The following changes since commit fb20871a54961b82d35303b43452928186c1361d:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../gregkh/staging-2.6

are available in the git repository at:

  git://git.monstr.eu/linux-2.6-microblaze.git for-linus

Arnd Bergmann (1):
      microblaze: remove init_mm

Michal Simek (1):
      microblaze: Add missing symbols for CONSTRUCTORS support

 arch/microblaze/kernel/init_task.c   |    2 --
 arch/microblaze/kernel/vmlinux.lds.S |   11 ++++++-----
 2 files changed, 6 insertions(+), 7 deletions(-)


diff --git a/arch/microblaze/kernel/init_task.c
b/arch/microblaze/kernel/init_task.c
index 48eb9fb..67da225 100644
--- a/arch/microblaze/kernel/init_task.c
+++ b/arch/microblaze/kernel/init_task.c
@@ -18,8 +18,6 @@
 
 static struct signal_struct init_signals = INIT_SIGNALS(init_signals);
 static struct sighand_struct init_sighand = INIT_SIGHAND(init_sighand);
-struct mm_struct init_mm = INIT_MM(init_mm);
-EXPORT_SYMBOL(init_mm);
 
 union thread_union init_thread_union
        __attribute__((__section__(".data.init_task"))) =
diff --git a/arch/microblaze/kernel/vmlinux.lds.S
b/arch/microblaze/kernel/vmlinux.lds.S
index 8ae807a..d34d38d 100644
--- a/arch/microblaze/kernel/vmlinux.lds.S
+++ b/arch/microblaze/kernel/vmlinux.lds.S
@@ -62,7 +62,8 @@ SECTIONS {
 
        _sdata = . ;
        .data ALIGN (4096) : { /* page aligned when MMU used - origin 0x4 */
-               *(.data)
+               DATA_DATA
+               CONSTRUCTORS
        }
        . = ALIGN(32);
        .data.cacheline_aligned : { *(.data.cacheline_aligned) }
@@ -98,13 +99,13 @@ SECTIONS {
        . = ALIGN(4096);
        .init.text : {
                _sinittext = . ;
-               *(.init.text)
-               *(.exit.text)
-               *(.exit.data)
+               INIT_TEXT
                _einittext = .;
        }
 
-       .init.data : { *(.init.data) }
+       .init.data : {
+               INIT_DATA
+       }
 
        . = ALIGN(4);
        .init.ivt : {


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854


                 reply	other threads:[~2009-06-20 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4A3CDCFE.9080200@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=adobriyan@gmail.com \
    --cc=arnd@arndb.de \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oberpar@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.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