From: David Howells <dhowells@redhat.com>
To: Tim Abbott <tabbott@ksplice.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 0/2] Linker script cleanup patches for frv
Date: Thu, 17 Sep 2009 14:01:21 +0100 [thread overview]
Message-ID: <8410.1253192481@redhat.com> (raw)
In-Reply-To: <1253119289-19261-1-git-send-email-tabbott@ksplice.com>
Tim Abbott <tabbott@ksplice.com> wrote:
> This is an updated version of the patch series I sent in late July
> cleaning up the frv 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.
Acked-by: David Howells <dhowells@redhat.com>
for both patches
prev parent reply other threads:[~2009-09-17 13:01 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 ` [PATCH v2 1/2] frv: remove unused .altinstructions code Tim Abbott
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 ` David Howells [this message]
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=8410.1253192481@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tabbott@ksplice.com \
/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