From: "Denys Dmytriyenko" <denis@denix.org>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: Jon Mason <jdmason@kudzu.us>, Diego Sueiro <diego.sueiro@arm.com>,
meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH] trusted-firmware-a: fiptool build using BUILD_CFLAGS and BUILD_LDFLAGS
Date: Fri, 12 Jun 2020 14:40:47 -0400 [thread overview]
Message-ID: <20200612184047.GS17660@denix.org> (raw)
In-Reply-To: <fb140298-1fe5-c166-d9eb-d71fa050ecea@gmail.com>
On Fri, Jun 12, 2020 at 10:45:20AM -0500, Joshua Watt wrote:
>
> On 6/12/20 8:00 AM, Jon Mason wrote:
> >On Fri, Jun 12, 2020 at 05:54:07AM -0700, Diego Sueiro wrote:
> >>On Fri, Jun 12, 2020 at 01:45 PM, Jon Mason wrote:
> >>
> >>>On Thu, Jun 11, 2020 at 03:17:04PM +0100, Diego Sueiro wrote:
> >>>>Since the TF-A fiptool is native tool we should be using the
> >>>>BUILD_CFLAGS and BUILD_LDFLAGS flags to proper build and execute it.
> >>>>
> >>>>Change-Id: I9634604dbc42ba7da85d9b9449f1ed94ecb38df2
> >>>>Issue-Id: SCM-888
> >>>>Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
> >>>Pulled into master.
> >>Thanks.
> >>
> >>Could you please backport it to dunfell?
> >Yes, this seems like a good bug fix. I just want to make sure that
> >Denys and Joshua are aware, since it might break them.
>
> Thanks for the heads up. I tested this on master with rock-pi-4 and
> qemuarm-secureboot, and everything looks OK.
I also tested this change against TI platforms and seems fine. Thanks.
--
Denys
next prev parent reply other threads:[~2020-06-12 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 14:17 [PATCH] trusted-firmware-a: fiptool build using BUILD_CFLAGS and BUILD_LDFLAGS Diego Sueiro
2020-06-12 12:45 ` [meta-arm] " Jon Mason
2020-06-12 12:54 ` Diego Sueiro
2020-06-12 13:00 ` [meta-arm] " Jon Mason
2020-06-12 15:45 ` Joshua Watt
2020-06-12 18:40 ` Denys Dmytriyenko [this message]
2020-06-15 12:57 ` Jon Mason
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=20200612184047.GS17660@denix.org \
--to=denis@denix.org \
--cc=diego.sueiro@arm.com \
--cc=jdmason@kudzu.us \
--cc=jpewhacker@gmail.com \
--cc=meta-arm@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.