From: Tim Abbott <tabbott@ksplice.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, Tim Abbott <tabbott@ksplice.com>,
Kyle McMartin <kyle@mcmartin.ca>, Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org
Subject: [PATCH v2 03/11] parisc: Remove useless altinstructions code copied from x86.
Date: Thu, 24 Sep 2009 10:36:18 -0400 [thread overview]
Message-ID: <1253802986-8132-4-git-send-email-tabbott@ksplice.com> (raw)
In-Reply-To: <1253802986-8132-1-git-send-email-tabbott@ksplice.com>
Signed-off-by: Tim Abbott <tabbott@ksplice.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Helge Deller <deller@gmx.de>
Cc: linux-parisc@vger.kernel.org
Acked-by: Sam Ravnborg <sam@ravnborg.org>
---
arch/parisc/kernel/vmlinux.lds.S | 25 -------------------------
1 files changed, 0 insertions(+), 25 deletions(-)
diff --git a/arch/parisc/kernel/vmlinux.lds.S b/arch/parisc/kernel/vmlinux.lds.S
index 3fd66d9..775be27 100644
--- a/arch/parisc/kernel/vmlinux.lds.S
+++ b/arch/parisc/kernel/vmlinux.lds.S
@@ -135,31 +135,6 @@ SECTIONS
INIT_TEXT_SECTION(16384)
INIT_DATA_SECTION(16)
- /* alternate instruction replacement. This is a mechanism x86 uses
- * to detect the CPU type and replace generic instruction sequences
- * with CPU specific ones. We don't currently do this in PA, but
- * it seems like a good idea...
- */
- . = ALIGN(4);
- .altinstructions : {
- __alt_instructions = .;
- *(.altinstructions)
- __alt_instructions_end = .;
- }
- .altinstr_replacement : {
- *(.altinstr_replacement)
- }
-
- /* .exit.text is discard at runtime, not link time, to deal with references
- * from .altinstructions and .eh_frame
- */
- .exit.text : {
- EXIT_TEXT
- }
- .exit.data : {
- EXIT_DATA
- }
-
PERCPU(PAGE_SIZE)
. = ALIGN(PAGE_SIZE);
__init_end = .;
--
1.6.3.3
next prev parent reply other threads:[~2009-09-24 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 14:36 [PATCH v2 00/11] Linker script cleanups for various architectures Tim Abbott
2009-09-24 14:36 ` [PATCH v2 01/11] Optimize the ordering of sections in RW_DATA_SECTION Tim Abbott
2009-09-24 14:36 ` [PATCH v2 02/11] parisc: Clean up linker script using new linker script macros Tim Abbott
2009-09-24 14:36 ` Tim Abbott [this message]
2009-09-24 14:36 ` [PATCH v2 04/11] xtensa: Cleanup " Tim Abbott
2009-09-24 14:36 ` [PATCH v2 05/11] um: Clean up linker script using standard macros Tim Abbott
2009-09-24 14:36 ` [PATCH v2 06/11] h8300: Cleanup linker script using new linker script macros Tim Abbott
2009-09-24 14:36 ` [PATCH v2 07/11] mn10300: Clean up linker script using higher-level macros Tim Abbott
2009-09-24 14:36 ` [PATCH v2 08/11] blackfin: Cleanup linker script using new linker script macros Tim Abbott
2009-09-24 14:36 ` [PATCH v2 09/11] powerpc: " Tim Abbott
2009-09-24 14:36 ` [PATCH v2 10/11] alpha: use .data.init_task instead of .data.init_thread Tim Abbott
2009-09-24 14:36 ` [PATCH v2 11/11] alpha: Clean up linker script using new linker script macros Tim Abbott
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=1253802986-8132-4-git-send-email-tabbott@ksplice.com \
--to=tabbott@ksplice.com \
--cc=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=sam@ravnborg.org \
--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
all inboxes | Powered by JetHome®