From: Andrew Stubbs <ams@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2.6.34-rc2] sh: Fix FDPIC binary loader
Date: Mon, 29 Mar 2010 08:23:00 +0000 [thread overview]
Message-ID: <4BB06364.4050909@codesourcery.com> (raw)
In-Reply-To: <4BAC849A.9090403@codesourcery.com>
On 29/03/10 04:15, Paul Mundt wrote:
> On Fri, Mar 26, 2010 at 09:55:38AM +0000, Andrew Stubbs wrote:
>> Ensure that the aux table is properly initialized, even when optional
>> features are missing. Without this, the FDPIC loader did not work.
>>
>> Signed-off-by: Andrew Stubbs<ams@codesourcery.com>
>
> This was whitespace damaged and didn't apply, so I did it by hand. Please
> double check your mailer settings for future patches, thanks.
Apologies for the mistake.
Thanks for taking the patch.
Andrew
next prev parent reply other threads:[~2010-03-29 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 9:55 [PATCH 2.6.34-rc2] sh: Fix FDPIC binary loader Andrew Stubbs
2010-03-29 3:15 ` Paul Mundt
2010-03-29 8:23 ` Andrew Stubbs [this message]
2012-11-16 10:07 ` Thomas Schwinge
2012-11-19 2:22 ` Paul Mundt
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=4BB06364.4050909@codesourcery.com \
--to=ams@codesourcery.com \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).