From: Ulrich Hecht <uli@fpond.eu>
To: kazunori.kobayashi@miraclelinux.com,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@denx.de" <pavel@denx.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"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:38:38 +0200 (CEST) [thread overview]
Message-ID: <165242228.250961.1756910318537@webmail.strato.de> (raw)
In-Reply-To: <42de8250-d98b-40e5-9e8a-d6bbb1ca8b6b@miraclelinux.com>
> On 09/03/2025 8:31 AM CEST Kazunori Kobayashi via lists.cip-project.org > I ran into the following compilation error with omap2plus_defconfig applied in this kernel version.
> | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c: In function 'ccdc_lsc_config': | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:452:3: error: implicit declaration of function 'dma_sync_sgtable_for_cpu'; did you mean 'dma_sync_single_for_cpu'? [-Werror=implicit-function-declaration] | dma_sync_sgtable_for_cpu(isp->dev, &req->table.sgt, | ^~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_cpu | CC [M] drivers/media/rc/keymaps/rc-avermedia-a16d.o | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:461:3: error: implicit declaration of function 'dma_sync_sgtable_for_device'; did you mean 'dma_sync_single_for_device'? [-Werror=implicit-function-declaration] | dma_sync_sgtable_for_device(isp->dev, &req->table.sgt, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_device
> It seems caused by the following change.
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/3483db997d491ba78957eb04743f6bb2ecc242aa
> This change seems merged from the 5.4 based kernel, but some other dependencies would also be needed to pass the compilation.
Thanks for the report.
Looks like it's missing "dma-mapping: add generic helpers for mapping sgtable objects". I pushed a backport to the rc tree (https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-st-rc), please check if it works.
I have also added omap2plus_defconfig to my local build configs.
CU
Uli
next prev parent reply other threads:[~2025-09-03 14:39 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
2025-09-03 16:21 ` Jan Kiszka
2025-09-03 14:38 ` Ulrich Hecht [this message]
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=165242228.250961.1756910318537@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