mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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>
Subject: Re: mainline build failure due to cf21f328fcaf ("media: nxp: Add i.MX8 ISI driver")
Date: Sun, 14 May 2023 12:59:32 +0200	[thread overview]
Message-ID: <55d5ec29-f30f-4596-a3b9-7e5b8adf0582@kernel.org> (raw)
In-Reply-To: <20230510090527.25e26127@sal.lan>

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

Hi Mauro,

Is you media staging tree included in LKP (kernel test robot)? You would
get huge build coverage after every push to your staging repo.

Except of maintainer trees, it is also useful to add there development
trees. That way for 'free' I can get early warnings about all my patches.

Best regards,
Krzysztof


  parent reply	other threads:[~2023-05-14 10:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 17:07 Sudip Mukherjee (Codethink)
2023-04-26 17:18 ` Sudip Mukherjee
2023-04-26 17:24 ` Laurent Pinchart
2023-05-08 10:54 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-08 16:27   ` Linus Torvalds
2023-05-10  8:05     ` Mauro Carvalho Chehab
2023-05-10  9:02       ` Linux regression tracking (Thorsten Leemhuis)
2023-05-11  6:46         ` Mauro Carvalho Chehab
2023-05-11  7:01           ` Laurent Pinchart
2023-05-10 13:16       ` Hans Verkuil
2023-05-14 10:59       ` Krzysztof Kozlowski [this message]
2023-05-15  7:46         ` Geert Uytterhoeven
2023-05-15  9:25           ` Mauro Carvalho Chehab
2023-05-15 10:00             ` Krzysztof Kozlowski
2023-05-15 14:55           ` Thorsten Leemhuis
2023-05-18 19:53     ` Nicolas Dufresne
2023-05-18 20:44       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55d5ec29-f30f-4596-a3b9-7e5b8adf0582@kernel.org \
    --to=krzk@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®