From: Greg Ungerer <gerg@snapgear.com>
To: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: [PATCH]: section names for m68k assembler routines, .text.init -> .init.text
Date: Thu, 05 Aug 2004 15:16:32 +1000 [thread overview]
Message-ID: <4111C2B0.809@snapgear.com> (raw)
Hi All,
In linux-2.6.7...
The section specifiers in the include/asm-m68k/init.h are
not the same as those used in the linker scripts. It currently
has .text.init while the linker scripts use .init.text. Same
goes for .data.init and .init.data. Looks like the init.h
is out of date...
Signed-of-by: Greg Ungerer <gerg@snapgear.com>
Regards
Greg
--- linux-2.6.x/include/asm-m68k/init.h.org 2002-02-28
09:01:48.000000000 +1000
+++ linux-2.6.x/include/asm-m68k/init.h 2004-08-05 14:52:23.000000000 +1000
@@ -1,11 +1,11 @@
#ifndef _M68K_INIT_H
#define _M68K_INIT_H
-#define __init __attribute__ ((__section__ (".text.init")))
-#define __initdata __attribute__ ((__section__ (".data.init")))
+#define __init __attribute__ ((__section__ (".init.text")))
+#define __initdata __attribute__ ((__section__ (".init.data")))
/* For assembly routines */
-#define __INIT .section ".text.init",#alloc,#execinstr
+#define __INIT .section ".init.text",#alloc,#execinstr
#define __FINIT .previous
-#define __INITDATA .section ".data.init",#alloc,#write
+#define __INITDATA .section ".init.data",#alloc,#write
#endif
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a CyberGuard Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
reply other threads:[~2004-08-05 5:17 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=4111C2B0.809@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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