From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arm-trusted-firmware: cleanup make target handling
Date: Thu, 15 Jun 2017 22:38:56 +0200 [thread overview]
Message-ID: <20170615223856.3bdee993@windsurf.lan> (raw)
In-Reply-To: <1497439347-10579-1-git-send-email-luca@lucaceresoli.net>
Hello,
On Wed, 14 Jun 2017 13:22:27 +0200, Luca Ceresoli wrote:
> ARM_TRUSTED_FIRMWARE_MAKE_TARGET is expanded, but it's never assigned
> so it is always empty. On the other hand the make targets are defined
> in ARM_TRUSTED_FIRMWARE_MAKE_OPTS, which should contain options, not
> targets.
>
> Clean it all up by moving the targets in the proper place, replacing
> the useless $(ARM_TRUSTED_FIRMWARE_MAKE_TARGET).
>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> ---
> boot/arm-trusted-firmware/arm-trusted-firmware.mk | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-06-15 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 11:22 [Buildroot] [PATCH] arm-trusted-firmware: cleanup make target handling Luca Ceresoli
2017-06-15 20:38 ` Thomas Petazzoni [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=20170615223856.3bdee993@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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