On Tue, Jun 04, 2024 at 11:50:20AM +0100, Jiaxun Yang wrote:
在2024年5月23日五月 下午4:43，Tom Rini写道：
On Thu, May 23, 2024 at 04:38:52PM +0100, Jiaxun Yang wrote:
在2024年5月23日五月 下午4:25，Tom Rini写道：
On Wed, May 22, 2024 at 04:34:43PM +0100, Jiaxun Yang wrote:
Hi all,
Sorry for flooding the mailing list recently, yet another huge RFC series ahead.
So after working on MIPS, arm64be and Xtensa I'm now on LoongArch, as suggested by Heinrich.
My big feedback here, and it applies to all of your other series as well, is to please update CI to make use of and test this. On the Docker side, update tools/docker/Dockerfile as needed. For Azure, you can tell it to use a different image and then follow the documentation on https://docs.u-boot.org/en/latest/develop/ci_testing.html and for GitLab you can at least use their "linter" to make sure that your additions have the correct syntax. Thanks.
Hi Tom,
Thanks for the feedback, I thought CI is for custodians only :-)
Do you mean I should include azure/gitlab pipeline file to create pipeline for those new qemu targets?
Yes, just like the rest of the QEMU targets.
Hi Tom,
I've got CI working on azure-pipeline for my arm64be, xtensa and LoongArch work.
What is the best way to submit all these changes? I think I can send patches to update Dockerfile and CI hooks first, then after new docker image being built I'll combine CI related changes into these series and refresh all those series.
Will it work for you?
Yes, please do a series that updates the Dockerfile and CI yaml files (do your best to update .gitlab-ci.yml as well, I'll fix it up if needed). Then say the other series depend on that previous one being applied. You can post an RFC patch or what have you that just changes to pointing at your test images instead and so long as it's a stand alone patch it's easy to drop. Thanks!