From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 2/2] [NEXT] edminiv2: enable relocation
Date: Mon, 11 Oct 2010 14:30:33 +0200 [thread overview]
Message-ID: <20101011123033.1AFEB14F310@gemini.denx.de> (raw)
In-Reply-To: <4CB2F82F.2090803@free.fr>
Dear Albert ARIBAUD,
In message <4CB2F82F.2090803@free.fr> you wrote:
>
> > If yes, then how about the other part of this series, "[PATCH V2 1/2]
> > [NEXT] orion5x: fix relocation-incompatible c..." ?
>
> I'd forgotten this one -- somehow I thought it was already applied since
> it was a fix made above Heiko's GOT relocation patches before they were
> merged from next to master.
>
> So yes, it is needed for relocation, but it is not ELF specific. It
> should thus go to the arm master branch, and the ELF branch should be
> based at or above it.
OK, will do.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
What is mind? No matter. What is matter? Never mind.
-- Thomas Hewitt Key, 1799-1875
next prev parent reply other threads:[~2010-10-11 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 19:49 [U-Boot] [PATCH V2 1/2] [NEXT] orion5x: fix relocation-incompatible code Albert Aribaud
2010-09-23 19:49 ` [U-Boot] [PATCH V2 2/2] [NEXT] edminiv2: enable relocation Albert Aribaud
2010-10-11 11:30 ` Wolfgang Denk
2010-10-11 11:42 ` Albert ARIBAUD
2010-10-11 11:47 ` Albert ARIBAUD
2010-10-11 12:29 ` Wolfgang Denk
2010-10-11 12:30 ` Wolfgang Denk [this message]
2010-09-27 5:52 ` [U-Boot] [PATCH V2 1/2] [NEXT] orion5x: fix relocation-incompatible code Prafulla Wadaskar
2010-09-27 6:34 ` Albert ARIBAUD
2010-09-27 6:36 ` Prafulla Wadaskar
2010-09-27 6:47 ` Albert ARIBAUD
2010-10-11 12:37 ` Wolfgang Denk
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=20101011123033.1AFEB14F310@gemini.denx.de \
--to=wd@denx.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