Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <ZElaVmxDsOkZj2DK@debian> <51cff63a-3a04-acf5-8264-bb19b0bee8a3@leemhuis.info>
 <CAHk-=wgzU8_dGn0Yg+DyX7ammTkDUCyEJ4C=NvnHRhxKWC7Wpw@mail.gmail.com>
 <20230510090527.25e26127@sal.lan> <55d5ec29-f30f-4596-a3b9-7e5b8adf0582@kernel.org>
In-Reply-To: <55d5ec29-f30f-4596-a3b9-7e5b8adf0582@kernel.org>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Mon, 15 May 2023 09:46:41 +0200
Message-ID: <CAMuHMdV=b8j=X3XEBWsAghsHrPT58xp7peaMiTZisqf7wRJf3w@mail.gmail.com>
Subject: Re: mainline build failure due to cf21f328fcaf ("media: nxp: Add
 i.MX8 ISI driver")
To:     Krzysztof Kozlowski <krzk@kernel.org>
Cc:     Mauro Carvalho Chehab <mchehab@kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Linux regressions mailing list <regressions@lists.linux.dev>,
        "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
        Shawn Guo <shawnguo@kernel.org>,
        Sascha Hauer <s.hauer@pengutronix.de>,
        NXP Linux Team <linux-imx@nxp.com>,
        linux-media@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org,
        Pengutronix Kernel Team <kernel@pengutronix.de>,
        Fabio Estevam <festevam@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Precedence: bulk

Hi Krzysztof,

On Sun, May 14, 2023 at 1:01 PM Krzysztof Kozlowski <krzk@kernel.org> 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@linux-m68k.org

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