Hi Krzysztof, On Sun, May 14, 2023 at 1:01 PM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: > On 10/05/2023 10:05, Mauro Carvalho Chehab wrote: > > And another CI job testing bisect breakages as I receive pull requests, > > applying patch per patch and using both allyesconfig and allmodconfig, > > also on x86_64 arch with W=1: > > > > https://builder.linuxtv.org/job/patchwork/ > > > > The rule is to not merge stuff on media tree if any of those jobs > > fail. I also fast-forward merging patches whose subject states that > > the build has failed. > > > > In order to help with that, on normal situation, I usually take one week > > to merge stuff from media_stage into media_tree, doing rebases at > > media_stage if needed to avoid git bisect build breakages at media_tree > > (which is from where I send my update PRs to you). > > > > Unfortunately, currently we don't have resources to do multiple randconfig > > Is you media staging tree included in LKP (kernel test robot)? You would > get huge build coverage after every push to your staging repo. As (multiple[*[) fixes for the build issues were submitted before the opening of the merge window, there must have been some build coverage, with even some people acting upon it... [*] General note, not limited to media: please apply build fixes and regression fixes ASAP, to avoid multiple people running into the same issues, and spending time on bisecting, investigating, fixing, ... Thanks a lot! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
