From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6FBE8C77B75 for ; Mon, 15 May 2023 09:27:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237900AbjEOJ1P (ORCPT ); Mon, 15 May 2023 05:27:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60928 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235649AbjEOJ0w (ORCPT ); Mon, 15 May 2023 05:26:52 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 337861708; Mon, 15 May 2023 02:25:34 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id C572161474; Mon, 15 May 2023 09:25:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CB94AC433D2; Mon, 15 May 2023 09:25:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684142732; bh=I/JHQf4eIEsXKezsZsMd1fV+aRLmrENZDEW/GBeFnBM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=IkcvM/nf4fogAbzM9g7VY/ONJN+bLvbZW8FynVvvFGqsI2oH7QiTGAHjnb5eil/qh dobgamg0SCITkPm7wwLMoRmDqJQSOdcHdPgBjbrzotay8LF23muG+3uwHPve5beoP6 00pd35Y0AvLPKt/AP5P0FQVMYkiWN4mDQyDvhSiZV5YboHWJmNIR08ABvYK1OMsOHY ZfYm1Ukq7iU6DRsmjg+gNVyj10kPpfQDoJlhdKLzL+zYFoCPPqRL7g5983Ym4k5HLh g6a1tOm5UVQiafQAf3g58jh1NZSnXiFF/N8Z+Ycu9OqMjpCvqN5DQJeFZLlVjVCbtS 8jhSybGaVDI/Q== Date: Mon, 15 May 2023 10:25:25 +0100 From: Mauro Carvalho Chehab To: Geert Uytterhoeven Cc: Krzysztof Kozlowski , Linus Torvalds , Linux regressions mailing list , "Sudip Mukherjee (Codethink)" , Laurent Pinchart , Shawn Guo , Sascha Hauer , NXP Linux Team , linux-media@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Pengutronix Kernel Team , Fabio Estevam Subject: Re: mainline build failure due to cf21f328fcaf ("media: nxp: Add i.MX8 ISI driver") Message-ID: <20230515102525.65150633@sal.lan> In-Reply-To: References: <51cff63a-3a04-acf5-8264-bb19b0bee8a3@leemhuis.info> <20230510090527.25e26127@sal.lan> <55d5ec29-f30f-4596-a3b9-7e5b8adf0582@kernel.org> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.37; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org Em Mon, 15 May 2023 09:46:41 +0200 Geert Uytterhoeven escreveu: > Hi Krzysztof, >=20 > On Sun, May 14, 2023 at 1:01=E2=80=AFPM Krzysztof Kozlowski wrote: > > On 10/05/2023 10:05, Mauro Carvalho Chehab wrote: =20 > > > And another CI job testing bisect breakages as I receive pull request= s, > > > applying patch per patch and using both allyesconfig and allmodconfig, > > > also on x86_64 arch with W=3D1: > > > > > > 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 w= eek > > > to merge stuff from media_stage into media_tree, doing rebases at > > > media_stage if needed to avoid git bisect build breakages at media_tr= ee > > > (which is from where I send my update PRs to you). > > > > > > Unfortunately, currently we don't have resources to do multiple randc= onfig =20 > > > > Is you media staging tree included in LKP (kernel test robot)? You would > > get huge build coverage after every push to your staging repo. =20 No idea, as I don't know where LKP settings are stored, nor what frequency it is doing builds from git://linuxtv.org/media_stage.git, if any. Do you k= now where we can check such configuration? In the end, patches there will end going to linux-next, so at least some sort of coverage is there, but I'm not sure if LKP will always reply to linux-media if the patch causing build regressions is there. While being helpful, one problem with LKP is that it is hard to filter out= =20 reports per git tree. The only way to check if the report is applicable to media trees seems to be looking inside the e-mail's body. > 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... >=20 > [*] 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! Fully agreed. That's why we opted to have a CI instance focused on media: we should be able to program it to give feedback with the kernel build parameters we use (Like W=3D1) and set it up in a way that it we can customize to our needs (like testing for the architectures where media drivers are known to be used in practice), and setting up an e-mail subject that can be easily be filtered by our e-mail filters. Regards, Mauro