From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Handle .gnu.hash section in ldscripts
Date: Tue, 28 Jan 2014 15:01:57 +0100 [thread overview]
Message-ID: <52E7B855.2080906@suse.de> (raw)
In-Reply-To: <20140127191148.51EF238033A@gemini.denx.de>
Dear Wolfgang Denk,
Am 27.01.2014 20:11, schrieb Wolfgang Denk:
> In message <52E6A96B.1080002@suse.de> you wrote:
>>
>> I figured out that the section was apparently not caught by the .gnu*
>> wildcard and this patch fixed our build for the following ARM configs:
>
> Do I understand you correctly that this fixes a _build_ error? So we
> can assume as long as the other archtiectures build fine, they are not
> affected by this?
Affirmative. :)
Best regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 16746 AG N?rnberg
next prev parent reply other threads:[~2014-01-28 14:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 4:48 [U-Boot] [PATCH] arm: Handle .gnu.hash section in ldscripts Andreas Färber
2014-01-27 14:24 ` Wolfgang Denk
2014-01-27 18:46 ` Andreas Färber
2014-01-27 19:11 ` Wolfgang Denk
2014-01-28 14:01 ` Andreas Färber [this message]
2014-01-28 16:03 ` Wolfgang Denk
2014-02-13 11:39 ` Albert ARIBAUD
2014-02-22 13:27 ` Albert ARIBAUD
2014-03-02 17:57 ` Andreas Färber
2014-03-02 19:15 ` Albert ARIBAUD
2014-03-02 20:57 ` Andreas Färber
2014-03-02 22:00 ` Andreas Färber
2014-03-02 23:44 ` Tom Rini
2014-03-03 6:58 ` Albert ARIBAUD
2014-03-03 7:00 ` Albert ARIBAUD
2014-03-09 20:05 ` Albert ARIBAUD
2014-03-09 20:22 ` Andreas Färber
2014-03-09 20:34 ` Albert ARIBAUD
2014-03-09 20:52 ` Andreas Färber
2014-03-10 7:24 ` Albert ARIBAUD
2014-03-13 15:43 ` Lukasz Majewski
2014-03-13 17:37 ` Albert ARIBAUD
2014-03-14 7:37 ` Lukasz Majewski
2014-03-19 9:33 ` Albert ARIBAUD
2014-03-03 8:41 ` Richard Biener
2014-03-03 13:25 ` Tom Rini
2014-03-25 2:08 ` Simon Glass
2014-04-07 9:43 ` Albert ARIBAUD
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=52E7B855.2080906@suse.de \
--to=afaerber@suse.de \
--cc=u-boot@lists.denx.de \
/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).