From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Chaplin, Kris" <Kris.Chaplin@amd.com>,
"O'Neal, Terry" <terry.oneal@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/1] configs/versal_vck190_defconfig: use Xilinx github for versal-firmware
Date: Tue, 7 Feb 2023 12:07:57 +0100 [thread overview]
Message-ID: <20230207120757.21504741@windsurf> (raw)
In-Reply-To: <CH2PR12MB50049CCA64BBFA96DE2553F9F0DB9@CH2PR12MB5004.namprd12.prod.outlook.com>
Hello,
On Tue, 7 Feb 2023 10:48:53 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Yes, I fully agree with you. We will have a proper firmware repo
> agnostic to ubuntu starting with our 2023.1 release.
>
> In the meantime, Terry O'Neal implemented this solution as a
> temporary one for 2022.2, so that we could get off of using my
> private github.
>
> I am confident that our 2023.1 solution will clean this up.
Sounds like a good plan, thanks for the details!
Best regards,
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
prev parent reply other threads:[~2023-02-07 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 10:53 [Buildroot] [PATCH v1 1/1] configs/versal_vck190_defconfig: use Xilinx github for versal-firmware Neal Frager via buildroot
2023-02-07 10:43 ` Thomas Petazzoni via buildroot
2023-02-07 10:48 ` Frager, Neal via buildroot
2023-02-07 11:07 ` Thomas Petazzoni via buildroot [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=20230207120757.21504741@windsurf \
--to=buildroot@buildroot.org \
--cc=Kris.Chaplin@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=terry.oneal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox