00:10 <Forty-Bot> shadows: if you compile it with networking support you can boot over TFTP

00:11 <Forty-Bot> shadows: see common/spl/spl_net.c

18:09 <dormito> what branch does the CI run off, master?

18:19 <Tartarus> Well, it runs on whatever triggered it

18:21 <Tartarus> There is duplicative CI in that I take a pull request, push to a "WIP" branch and CI checks that (and I check it with other things) and then push to master if it's good and CI runs again (since I haven't seen a way to have Gitlab nor Azure be smart and say "I already tested this!" and I'm too lazy to automate telling Gitlab or Azure to not run in that case.

18:27 <dormito> how about for submitted patches?

18:28 <Tartarus> Ah, so there's nothing automated for mailing list submission (CI is too resource heavy for that), but you can trigger CI will pull requests on github

18:28 <Tartarus> See https://docs.u-boot.org/en/latest/develop/ci_testing.html#azure-pipelines for more details

18:34 <dormito> ah ok. So someone mentioning build failures on the CI could (for a patch series) could simply be asking for a rebase?

18:36 <Tartarus> Well, rebase and at least check that the reported failure doesn't exist locally before re-posting

18:36 <dormito> yeah (in my mind, a rebase nessicarily includes a "does it build & function" check :p)