From: Ulrich Hecht <uli@fpond.eu>
To: jan.kiszka@siemens.com,
Kazunori Kobayashi <kazunori.kobayashi@miraclelinux.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@denx.de" <pavel@denx.de>,
"masami.ichikawa@cybertrust.co.jp"
<masami.ichikawa@cybertrust.co.jp>,
"chris.paterson2@renesas.com" <chris.paterson2@renesas.com>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123
Date: Wed, 3 Sep 2025 16:46:45 +0200 (CEST) [thread overview]
Message-ID: <1208303079.251954.1756910805287@webmail.strato.de> (raw)
In-Reply-To: <7a864d4e-3051-493c-a64a-cfda61c92936@siemens.com>
> On 09/03/2025 12:36 PM CEST Jan Kiszka via lists.cip-project.org <jan.kiszka=siemens.com@lists.cip-project.org> wrote:
> General question: Is that build breakage above not triggerable via the
> cip-kernel-configs?
CONFIG_VIDEO_OMAP3 is not enabled in any CIP configs.
> If so, you likely want to make sure that it is. If
> it was triggerable already, then we should try to understand why it was
> missed.
We could enable all the defconfigs; I think that discussion has already happened some time ago, though I don't remember the outcome. :)
I keep a bunch of local configs that cover all sorts of unsupported stuff (m68k etc.) that I build before pushing a kernel to make sure nothing breaks needlessly. I have added omap2plus_defconfig to that.
CU
Uli
next prev parent reply other threads:[~2025-09-03 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 15:21 [ANNOUNCE] Release v4.19.325-cip123 Ulrich Hecht
2025-09-03 6:31 ` [cip-dev] " Kazunori Kobayashi
2025-09-03 10:36 ` Jan Kiszka
2025-09-03 14:46 ` Ulrich Hecht [this message]
2025-09-03 16:21 ` Jan Kiszka
2025-09-03 14:38 ` Ulrich Hecht
2025-09-03 23:35 ` nobuhiro.iwamatsu.x90
2025-09-04 3:32 ` Kazunori Kobayashi
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=1208303079.251954.1756910805287@webmail.strato.de \
--to=uli@fpond.eu \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=kazunori.kobayashi@miraclelinux.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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