From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/1] board/zynqmp: fix atf build failure
Date: Mon, 31 Jul 2023 18:07:23 +0200 [thread overview]
Message-ID: <20230731180723.2ac1d93f@windsurf> (raw)
In-Reply-To: <CH2PR12MB5004F616135C586B599F520DF005A@CH2PR12MB5004.namprd12.prod.outlook.com>
On Mon, 31 Jul 2023 16:01:45 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Thank you for pointing this out. Are you ok with my just creating a
> link to the arm-trusted-firmware patch for v2.6 already included in
> buildroot?
I saw your patch that use a symbolic link. I don't have a strong
opinion here. On one side, using a symbolic link obviously avoids
duplicating the patch. However, I'm wondering if we will remember to
adjust the symlink in board/zynqmp and board/versal when we
change/remove the patches in boot/arm-trusted/firmware/. Or maybe
AMD/Xilinx will update to a newer TF-A soon, which will no longer
require the bug fix?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-31 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 6:11 [Buildroot] [PATCH v1 1/1] board/zynqmp: fix atf build failure Neal Frager via buildroot
2023-07-31 12:11 ` Luca Ceresoli via buildroot
2023-07-31 12:21 ` Thomas Petazzoni via buildroot
2023-07-31 16:01 ` Frager, Neal via buildroot
2023-07-31 16:07 ` Thomas Petazzoni via buildroot [this message]
2023-07-31 16:17 ` Frager, Neal via buildroot
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=20230731180723.2ac1d93f@windsurf \
--to=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.com \
/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.