public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Tim Abbott <tabbott@ksplice.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Roman Zippel <zippel@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sam Ravnborg <sam@ravnborg.org>, Tim Abbott <tabbott@ksplice.com>
Subject: [PATCH v2 0/2] Linker script cleanup patches for m68k
Date: Wed, 16 Sep 2009 12:44:24 -0400	[thread overview]
Message-ID: <1253119466-19488-1-git-send-email-tabbott@ksplice.com> (raw)

This is an updated version of the patch series I sent on September 6
cleaning up the m68k architecture's linker scripts.  The only change is
that it is rebased on top of Linus's current master.

This cross-architecture linker script cleanup project is in
preparation for adding support for building the kernel with
-ffunction-sections -fdata-sections, which is a prerequisite for
Ksplice.

Tim Abbott (2):
  m68k: Make thread_info.h usable from assembly.
  m68k: Cleanup linker scripts using new linker script macros.

 arch/m68k/include/asm/thread_info_mm.h |    2 +
 arch/m68k/kernel/vmlinux-std.lds       |   53 ++++++-------------------------
 arch/m68k/kernel/vmlinux-sun3.lds      |   53 ++++++--------------------------
 3 files changed, 23 insertions(+), 85 deletions(-)

             reply	other threads:[~2009-09-16 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:44 Tim Abbott [this message]
2009-09-16 16:44 ` [PATCH v2 1/2] m68k: Make thread_info.h usable from assembly Tim Abbott
2009-09-27  9:55   ` Geert Uytterhoeven
2009-09-27 11:58     ` Sam Ravnborg
2009-11-20  7:56       ` Geert Uytterhoeven
2009-09-16 16:44 ` [PATCH v2 2/2] m68k: Cleanup linker scripts using new linker script macros Tim Abbott
2009-09-27  9:58   ` Geert Uytterhoeven
2009-09-27 13:01     ` Andreas Schwab
2009-09-27 17:57       ` Tim Abbott
2009-09-29 17:12         ` Andreas Schwab
2009-09-30  6:53           ` Sam Ravnborg

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=1253119466-19488-1-git-send-email-tabbott@ksplice.com \
    --to=tabbott@ksplice.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zippel@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