From: Tejun Heo <tj@kernel.org>
To: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Michal Simek <monstr@monstr.eu>,
	microblaze-uclinux@itee.uq.edu.au, Sam
Subject: [PATCH percpu 1/2] microblaze: include EXIT_TEXT to _stext
Date: Wed, 08 Jul 2009 18:26:30 +0900	[thread overview]
Message-ID: <4A546646.70305@kernel.org> (raw)
From: Michal Simek <monstr@monstr.eu>
Microblaze wants to throw out EXIT_TEXT during runtime too.  This
hasn't caused trouble till now because the linker script didn't
discard EXIT_TEXT and it ended up in its default output section.  As
discard definition is about to be unified, include EXIT_TEXT into
_stext explicitly and while at it replace explicit exitcall definition
to EXIT_CALL.
Signed-off-by: Michal Simek <monstr@monstr.eu>
Signed-off-by: Tejun Heo <tj@kernel.org>
---
Michal, I added the commit messaeg and SOB.  If you don't like it
please let me know.
If there's no further objection, I'll commit this and the next patch
to percpu#for-next.
Thanks.
 arch/microblaze/kernel/vmlinux.lds.S |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Index: work/arch/microblaze/kernel/vmlinux.lds.S
===================================================================
--- work.orig/arch/microblaze/kernel/vmlinux.lds.S
+++ work/arch/microblaze/kernel/vmlinux.lds.S
@@ -23,8 +23,8 @@ SECTIONS {
 		_stext = . ;
 		*(.text .text.*)
 		*(.fixup)
-
-		*(.exitcall.exit)
+               EXIT_TEXT
+               EXIT_CALL
 		SCHED_TEXT
 		LOCK_TEXT
 		KPROBES_TEXT
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Michal Simek <monstr@monstr.eu>,
	microblaze-uclinux@itee.uq.edu.au,
	Sam Ravnborg <sam@ravnborg.org>, Paul Mundt <lethal@linux-sh.org>,
	Tony Luck <tony.luck@intel.com>,
	Mike Frysinger <vapier@gentoo.org>
Subject: [PATCH percpu 1/2] microblaze: include EXIT_TEXT to _stext
Date: Wed, 08 Jul 2009 18:26:30 +0900	[thread overview]
Message-ID: <4A546646.70305@kernel.org> (raw)
Message-ID: <20090708092630.stQmmedpKZc6z4BFpp1DX73xy6DDftCqRiaf9erDKqc@z> (raw)
From: Michal Simek <monstr@monstr.eu>
Microblaze wants to throw out EXIT_TEXT during runtime too.  This
hasn't caused trouble till now because the linker script didn't
discard EXIT_TEXT and it ended up in its default output section.  As
discard definition is about to be unified, include EXIT_TEXT into
_stext explicitly and while at it replace explicit exitcall definition
to EXIT_CALL.
Signed-off-by: Michal Simek <monstr@monstr.eu>
Signed-off-by: Tejun Heo <tj@kernel.org>
---
Michal, I added the commit messaeg and SOB.  If you don't like it
please let me know.
If there's no further objection, I'll commit this and the next patch
to percpu#for-next.
Thanks.
 arch/microblaze/kernel/vmlinux.lds.S |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Index: work/arch/microblaze/kernel/vmlinux.lds.S
===================================================================
--- work.orig/arch/microblaze/kernel/vmlinux.lds.S
+++ work/arch/microblaze/kernel/vmlinux.lds.S
@@ -23,8 +23,8 @@ SECTIONS {
 		_stext = . ;
 		*(.text .text.*)
 		*(.fixup)
-
-		*(.exitcall.exit)
+               EXIT_TEXT
+               EXIT_CALL
 		SCHED_TEXT
 		LOCK_TEXT
 		KPROBES_TEXT
next             reply	other threads:[~2009-07-08  9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  9:26 Tejun Heo [this message]
2009-07-08  9:26 ` [PATCH percpu 1/2] microblaze: include EXIT_TEXT to _stext Tejun Heo
2009-07-08  9:27 ` [PATCH 2/2] linker script: unify usage of discard definition Tejun Heo
2009-07-08  9:27   ` Tejun Heo
2009-07-17 21:13   ` Sam Ravnborg
2009-07-17 21:13     ` Sam Ravnborg
2009-07-08 10:37 ` [PATCH percpu 1/2] microblaze: include EXIT_TEXT to _stext Michal Simek
2009-07-09  2:28   ` Tejun Heo
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=4A546646.70305@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@monstr.eu \
    /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;
as well as URLs for NNTP newsgroup(s).