From: Tim Abbott <tabbott@ksplice.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Nelson Elhage <nelhage@ksplice.com>,
Tim Abbott <tabbott@ksplice.com>,
David Howells <dhowells@redhat.com>
Subject: [PATCH v2 1/2] frv: remove unused .altinstructions code
Date: Wed, 16 Sep 2009 12:41:28 -0400 [thread overview]
Message-ID: <1253119289-19261-2-git-send-email-tabbott@ksplice.com> (raw)
In-Reply-To: <1253119289-19261-1-git-send-email-tabbott@ksplice.com>
From: Nelson Elhage <nelhage@ksplice.com>
It appears that frv copied the .altinstructions definitions in its linker
script from x86. Since frv doesn't put anything in those sections, this
is just dead code.
Signed-off-by: Nelson Elhage <nelhage@ksplice.com>
Signed-off-by: Tim Abbott <tabbott@ksplice.com>
Cc: David Howells <dhowells@redhat.com>
---
arch/frv/kernel/vmlinux.lds.S | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/arch/frv/kernel/vmlinux.lds.S b/arch/frv/kernel/vmlinux.lds.S
index 7dbf41f..cfb4181 100644
--- a/arch/frv/kernel/vmlinux.lds.S
+++ b/arch/frv/kernel/vmlinux.lds.S
@@ -51,11 +51,6 @@ SECTIONS
.con_initcall.init : { *(.con_initcall.init) }
__con_initcall_end = .;
SECURITY_INIT
- . = ALIGN(4);
- __alt_instructions = .;
- .altinstructions : { *(.altinstructions) }
- __alt_instructions_end = .;
- .altinstr_replacement : { *(.altinstr_replacement) }
PERCPU(4096)
--
1.6.3.3
next prev parent reply other threads:[~2009-09-16 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 16:41 [PATCH v2 0/2] Linker script cleanup patches for frv Tim Abbott
2009-09-16 16:41 ` Tim Abbott [this message]
2009-09-16 16:41 ` [PATCH v2 2/2] frv: clean up linker script using new linker script macros Tim Abbott
2009-09-17 13:01 ` [PATCH v2 0/2] Linker script cleanup patches for frv David Howells
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=1253119289-19261-2-git-send-email-tabbott@ksplice.com \
--to=tabbott@ksplice.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nelhage@ksplice.com \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®