From: "Hans Verkuil" <hverkuil-cisco@xs4all.nl>
To: linux-media@vger.kernel.org
Subject: cron job: media_tree daily build: ABI WARNING
Date: Tue, 30 Apr 2024 03:51:17 +0200 [thread overview]
Message-ID: <20240430015119.89486C116B1@smtp.kernel.org> (raw)
This message is generated daily by a cron job that builds media_tree for
the architectures in the list below.
Results of the daily build of media_tree:
date: Tue Apr 30 03:00:24 CEST 2024
media-tree git repo: git://linuxtv.org/hverkuil/media_tree.git
media-tree git branch: media_stage/master
media-tree git hash: 1c73d0b29d04bf4082e7beb6a508895e118ee30d
v4l-utils git hash: dd049328e5282f478ba543a50dcb14618782abbb
edid-decode git hash: 3d635499e4aca3319f0796ba787213c981c5a770
gcc version: i686-linux-gcc (GCC) 13.2.0
smatch/sparse repo: git://repo.or.cz/smatch.git
smatch version: v0.5.0-8639-gff1cc4d4
sparse version: v0.5.0-8639-gff1cc4d4
build-scripts repo: https://git.linuxtv.org/hverkuil/build-scripts.git
build-scripts git hash: 00e599f8286b7f05e7c8c99b9e7caf4e21fc58b6
host hardware: x86_64
host os: 6.5.0-26-generic
linux-git-arm: OK
linux-git-arm64: OK
linux-git-powerpc64: OK
linux-git-i686: OK
linux-git-x86_64: OK
no-of.config: OK
no-acpi.config: OK
no-pm.config: OK
no-pm-sleep.config: OK
no-debug-fs.config: OK
sparse: OK
smatch: WARNINGS:
drivers/media/test-drivers/vivid/vivid-core.c:1989 vivid_create_instance() parse error: turning off implications after 60 seconds
drivers/media/usb/em28xx/em28xx-video.c:2866 em28xx_v4l2_init() parse error: turning off implications after 60 seconds
COMPILE_TEST: OK
strcpy/strncpy/strlcpy: OK
abi-compliance: ABI WARNING: changed for arm powerpc64
pahole: ABI OK
utils: OK
spec-git: OK
kerneldoc: OK
date: Tue Apr 30 03:14:05 CEST 2024
virtme-64: WARNINGS: Final Summary: 3413, Succeeded: 3413, Failed: 0, Warnings: 2
virtme-32: OK: Final Summary: 3546, Succeeded: 3546, Failed: 0, Warnings: 0
date: Tue Apr 30 03:50:15 CEST 2024
Detailed results are available here:
https://hverkuil.home.xs4all.nl/logs/Tuesday.log
Detailed regression test results are available here:
https://hverkuil.home.xs4all.nl/logs/Tuesday-test-media-64.log
https://hverkuil.home.xs4all.nl/logs/Tuesday-test-media-64-dmesg.log
https://hverkuil.home.xs4all.nl/logs/Tuesday-test-media-32.log
https://hverkuil.home.xs4all.nl/logs/Tuesday-test-media-32-dmesg.log
Full logs are available here:
https://hverkuil.home.xs4all.nl/logs/Tuesday.tar.bz2
The Media Infrastructure API from this daily build is here:
https://hverkuil.home.xs4all.nl/spec/index.html
next reply other threads:[~2024-04-30 1:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 1:51 Hans Verkuil [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-22 4:43 cron job: media_tree daily build: ABI WARNING Hans Verkuil
2018-02-21 4:43 Hans Verkuil
2018-02-20 4:44 Hans Verkuil
2018-02-20 12:51 ` Hans Verkuil
2018-02-17 4:50 Hans Verkuil
2018-02-17 9:07 ` Hans Verkuil
2017-04-16 4:19 Hans Verkuil
2016-09-13 3:07 Hans Verkuil
2016-03-20 4:01 Hans Verkuil
2016-03-20 9:54 ` Hans Verkuil
2015-03-24 3:46 Hans Verkuil
2015-02-28 3:45 Hans Verkuil
2015-02-20 3:45 Hans Verkuil
2015-02-19 3:44 Hans Verkuil
2015-02-18 3:45 Hans Verkuil
2015-02-17 3:44 Hans Verkuil
2014-12-06 3:43 Hans Verkuil
2014-07-22 6:26 Hans Verkuil
2014-07-18 2:45 Hans Verkuil
2014-05-26 2:43 Hans Verkuil
2013-11-13 3:32 Hans Verkuil
2013-11-13 7:26 ` Hans Verkuil
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=20240430015119.89486C116B1@smtp.kernel.org \
--to=hverkuil-cisco@xs4all.nl \
--cc=linux-media@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).