From: kernel test robot <lkp@intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org
Subject: [sailus-media-tree:frame-desc] BUILD SUCCESS WITH WARNING 7c1e8e3f907ccd6c51f2c23e1a4ac09b6d4b1f04
Date: Tue, 25 Aug 2026 08:37:54 +0800 [thread overview]
Message-ID: <202608250840.0IWsSMuv-lkp@intel.com> (raw)
tree/branch: git://linuxtv.org/sailus/media_tree.git frame-desc
branch HEAD: 7c1e8e3f907ccd6c51f2c23e1a4ac09b6d4b1f04 media: j721e-csi2rx: Use v4l2_subdev_get_frame_desc()
Warning (recently discovered and may have been fixed):
https://lore.kernel.org/oe-kbuild-all/202608242201.UypJNTA2-lkp@intel.com
https://lore.kernel.org/oe-kbuild-all/202608242231.UUc2L5th-lkp@intel.com
drivers/media/platform/nxp/imx8-isi/imx8-isi-crossbar.c:51:25: warning: format '%p' expects argument of type 'void *', but argument 5 has type 'long int' [-Wformat=]
drivers/media/platform/rockchip/rkisp1/rkisp1-isp.c:109:25: warning: format '%p' expects argument of type 'void *', but argument 5 has type 'long int' [-Wformat=]
Warning ids grouped by kconfigs:
recent_errors
|-- arc-allmodconfig
| `-- drivers-media-platform-nxp-imx8-isi-imx8-isi-crossbar.c:warning:format-p-expects-argument-of-type-void-but-argument-has-type-long-int
`-- parisc-allmodconfig
`-- drivers-media-platform-rockchip-rkisp1-rkisp1-isp.c:warning:format-p-expects-argument-of-type-void-but-argument-has-type-long-int
elapsed time: 775m
configs tested: 15
configs skipped: 1
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
alpha defconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
csky allmodconfig gcc-16.1.0
i386 allmodconfig gcc-14
loongarch defconfig clang-24
loongarch loongson32_defconfig clang-18
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
parisc allmodconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
parisc defconfig gcc-16.1.0
sh defconfig gcc-16.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-25 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608250840.0IWsSMuv-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.