From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: any value in centralizing common 32/64 x86 content in vmlinux.lds.S?
Date: Sun, 2 Dec 2007 03:08:58 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0712020301180.29501@localhost.localdomain> (raw)
given the amount of common content between
arch/x86/kernel/vmlinux_32.lds.S and arch/x86/kernel/vmlinux_64.lds.S,
what about just defining macros for some of that stuff in
arch/x86/kernel/vmlinux.lds.S and cutting down on all the duplication?
as is done in include/asm-generic/vmlinux.lds.S, why not just
define some handy macros, like:
#define INITRAMFS(align) \
. = ALIGN(align); \
.init.ramfs : AT(ADDR(.init.ramfs) - LOAD_OFFSET) { \
__initramfs_start = .; \
*(.init.ramfs) \
__initramfs_end = .; \
}
or something similar.
i'm guessing there's a fair amount of content like that that can be
coalesced, no? it would also standardize some of the niggling
differences between some of that content between the two files.
rday
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
reply other threads:[~2007-12-02 8:09 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=alpine.LFD.0.9999.0712020301180.29501@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@vger.kernel.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®