From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dan Carpenter" <dan.carpenter@linaro.org>, stable@vger.kernel.org
Cc: "laurent.pinchart" <laurent.pinchart@ideasonboard.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: randconfig fixes for 5.10.y
Date: Tue, 30 May 2023 10:53:55 +0200 [thread overview]
Message-ID: <4716f9fd-0e09-4e69-a802-09ddecff2733@app.fastmail.com> (raw)
In-Reply-To: <b59d1bfe-15b1-4318-a12f-a38143ba35bd@kili.mountain>
On Tue, May 30, 2023, at 10:22, Dan Carpenter wrote:
>
> I'm going to be doing regular randconfig testing on stable so let me
> know if you have any advice.
Just one thing: In my spot for random projects, I occasionally
publish my latest "randconfig-*" branch, which may help you figure
out if I have seen a particular build failure before:
https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/refs/heads
This tree should build without any warnings or errors on arm, arm64
and x86, so if you run into something that you can't immediately
see if it as a fix already, you can try bisecting against the
latest branch there to see how I addressed it locally or upstream.
It's a mix of patches that I submitted already but were not picked
up yet, that might need a minor rework based on comments, or that
are not acceptable for one reason or another.
Arnd
next prev parent reply other threads:[~2023-05-30 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:22 randconfig fixes for 5.10.y Dan Carpenter
2023-05-30 8:53 ` Arnd Bergmann [this message]
2023-05-30 15:38 ` Dan Carpenter
2023-05-30 19:02 ` Arnd Bergmann
2023-05-30 19:20 ` Arnd Bergmann
2023-05-31 10:12 ` Arnd Bergmann
2023-05-31 16:37 ` Nick Desaulniers
2023-06-07 17:55 ` Greg KH
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=4716f9fd-0e09-4e69-a802-09ddecff2733@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.org \
--cc=stable@vger.kernel.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