From: Trevor Woerner <twoerner@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@lists.yoctoproject.org, Jon Mason <jon.mason@arm.com>,
Ross Burton <ross.burton@arm.com>
Subject: Re: [meta-rockchip][PATCH] trusted-firmware-a: Pin to use gcc for now
Date: Fri, 10 Dec 2021 00:40:20 -0500 [thread overview]
Message-ID: <20211210054019.GA40862@localhost> (raw)
In-Reply-To: <20211210011458.1664766-1-raj.khem@gmail.com>
On Thu 2021-12-09 @ 05:14:58 PM, Khem Raj wrote:
> tf-a built with clang is bloated for rk3399 SOCs with 2.6+
> it needs looking into, until then use gcc always to build it
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Cc: Jon Mason <jon.mason@arm.com>
> Cc: Ross Burton <ross.burton@arm.com>
> ---
> .../trusted-firmware-a/trusted-firmware-a_%.bbappend | 7 +++++++
> 1 file changed, 7 insertions(+)
Applied to meta-rockchip master. Thanks!
prev parent reply other threads:[~2021-12-10 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 1:14 [meta-rockchip][PATCH] trusted-firmware-a: Pin to use gcc for now Khem Raj
2021-12-10 5:40 ` Trevor Woerner [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=20211210054019.GA40862@localhost \
--to=twoerner@gmail.com \
--cc=jon.mason@arm.com \
--cc=raj.khem@gmail.com \
--cc=ross.burton@arm.com \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox