From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Divides variable of linker flags to LDFLAGS-u-boot and LDFLAGS
Date: Mon, 11 Apr 2011 14:24:59 -0500 [thread overview]
Message-ID: <20110411142459.1cd11e2b@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <20110411191543.B9F22151F83@gemini.denx.de>
On Mon, 11 Apr 2011 21:15:43 +0200
Wolfgang Denk <wd@denx.de> wrote:
> Dear Nobuhiro Iwamatsu,
>
> In message <1294747652-12603-1-git-send-email-iwamatsu@nigauri.org> you wrote:
> > Linker needs to use the proper endian/bfd flags even when doing partial linking.
> > LDFLAGS_u-boot sets linker option which is called it when U-boot is built
> > (u-boot final).
> > LDFLAGS sets necessary option by partial linking (use in cmd_link_o_target).
> >
> > CC: Mike Frysinger <vapier@gentoo.org>
> > Signed-off-by: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
> > ---
> > V3: Remove trailing space.
> >
> > Makefile | 2 +-
> > arch/blackfin/config.mk | 3 ++-
> > arch/i386/config.mk | 3 ++-
> > arch/nios2/config.mk | 2 +-
> > arch/powerpc/config.mk | 4 ++--
> > arch/sh/config.mk | 2 +-
> > arch/sh/cpu/sh2/config.mk | 4 +++-
> > config.mk | 8 +++++---
> > 8 files changed, 17 insertions(+), 11 deletions(-)
>
> This patch does no longer apply. Is it still needed? If yes, please
> rebase and resubmit. Thanks.
It's already been applied (8aba9dceebb14144e07d19593111ee3a999c37fc)...
-Scott
next prev parent reply other threads:[~2011-04-11 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:07 [U-Boot] [PATCH v3] Divides variable of linker flags to LDFLAGS-u-boot and LDFLAGS Nobuhiro Iwamatsu
2011-01-12 23:23 ` Mike Frysinger
2011-04-11 19:15 ` Wolfgang Denk
2011-04-11 19:24 ` Scott Wood [this message]
2011-04-13 2:01 ` Nobuhiro Iwamatsu
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=20110411142459.1cd11e2b@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--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