From: "Hans Verkuil" <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Subject: [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: WARNINGS
Date: Tue, 23 Mar 2010 21:37:30 +0100 (CET) [thread overview]
Message-ID: <201003232037.o2NKbUXQ037751@smtp-vbr14.xs4all.nl> (raw)
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date: Tue Mar 23 19:00:28 CET 2010
path: http://www.linuxtv.org/hg/v4l-dvb
changeset: 14502:a79dd2ae4d0e
git master: f6760aa024199cfbce564311dc4bc4d47b6fb349
git media-master: 8c69c6ed6c74c94fa7ad6fa24eda452e4b212d81
gcc version: i686-linux-gcc (GCC) 4.4.3
host hardware: x86_64
host os: 2.6.32.5
linux-2.6.32.6-armv5: OK
linux-2.6.33-armv5: OK
linux-2.6.34-rc1-armv5: OK
linux-2.6.32.6-armv5-davinci: WARNINGS
linux-2.6.33-armv5-davinci: WARNINGS
linux-2.6.34-rc1-armv5-davinci: WARNINGS
linux-2.6.32.6-armv5-ixp: WARNINGS
linux-2.6.33-armv5-ixp: WARNINGS
linux-2.6.34-rc1-armv5-ixp: WARNINGS
linux-2.6.32.6-armv5-omap2: WARNINGS
linux-2.6.33-armv5-omap2: WARNINGS
linux-2.6.34-rc1-armv5-omap2: WARNINGS
linux-2.6.22.19-i686: WARNINGS
linux-2.6.23.17-i686: WARNINGS
linux-2.6.24.7-i686: WARNINGS
linux-2.6.25.20-i686: WARNINGS
linux-2.6.26.8-i686: WARNINGS
linux-2.6.27.44-i686: WARNINGS
linux-2.6.28.10-i686: WARNINGS
linux-2.6.29.1-i686: WARNINGS
linux-2.6.30.10-i686: WARNINGS
linux-2.6.31.12-i686: WARNINGS
linux-2.6.32.6-i686: WARNINGS
linux-2.6.33-i686: WARNINGS
linux-2.6.34-rc1-i686: WARNINGS
linux-2.6.32.6-m32r: OK
linux-2.6.33-m32r: OK
linux-2.6.34-rc1-m32r: OK
linux-2.6.32.6-mips: WARNINGS
linux-2.6.33-mips: WARNINGS
linux-2.6.34-rc1-mips: WARNINGS
linux-2.6.32.6-powerpc64: WARNINGS
linux-2.6.33-powerpc64: WARNINGS
linux-2.6.34-rc1-powerpc64: WARNINGS
linux-2.6.22.19-x86_64: WARNINGS
linux-2.6.23.17-x86_64: WARNINGS
linux-2.6.24.7-x86_64: WARNINGS
linux-2.6.25.20-x86_64: WARNINGS
linux-2.6.26.8-x86_64: WARNINGS
linux-2.6.27.44-x86_64: WARNINGS
linux-2.6.28.10-x86_64: WARNINGS
linux-2.6.29.1-x86_64: WARNINGS
linux-2.6.30.10-x86_64: WARNINGS
linux-2.6.31.12-x86_64: WARNINGS
linux-2.6.32.6-x86_64: WARNINGS
linux-2.6.33-x86_64: WARNINGS
linux-2.6.34-rc1-x86_64: WARNINGS
linux-git-armv5: OK
linux-git-armv5-davinci: OK
linux-git-armv5-ixp: OK
linux-git-armv5-omap2: OK
linux-git-i686: WARNINGS
linux-git-m32r: OK
linux-git-mips: OK
linux-git-powerpc64: WARNINGS
linux-git-x86_64: WARNINGS
spec: ERRORS
spec-git: OK
sparse: ERRORS
linux-2.6.16.62-i686: WARNINGS
linux-2.6.17.14-i686: WARNINGS
linux-2.6.18.8-i686: WARNINGS
linux-2.6.19.7-i686: WARNINGS
linux-2.6.20.21-i686: WARNINGS
linux-2.6.21.7-i686: WARNINGS
linux-2.6.16.62-x86_64: WARNINGS
linux-2.6.17.14-x86_64: WARNINGS
linux-2.6.18.8-x86_64: WARNINGS
linux-2.6.19.7-x86_64: WARNINGS
linux-2.6.20.21-x86_64: WARNINGS
linux-2.6.21.7-x86_64: WARNINGS
Detailed results are available here:
http://www.xs4all.nl/~hverkuil/logs/Tuesday.log
Full logs are available here:
http://www.xs4all.nl/~hverkuil/logs/Tuesday.tar.bz2
The V4L-DVB specification from this daily build is here:
http://www.xs4all.nl/~hverkuil/spec/media.html
next reply other threads:[~2010-03-23 20:37 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 20:37 Hans Verkuil [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-04 19:39 [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: WARNINGS Hans Verkuil
2010-05-03 19:39 Hans Verkuil
2010-05-02 19:39 Hans Verkuil
2010-05-01 19:39 Hans Verkuil
2010-04-30 19:39 Hans Verkuil
2010-04-29 19:39 Hans Verkuil
2010-04-28 19:38 Hans Verkuil
2010-04-27 19:38 Hans Verkuil
2010-04-26 19:39 Hans Verkuil
2010-04-25 19:39 Hans Verkuil
2010-04-24 19:43 Hans Verkuil
2010-04-23 19:42 Hans Verkuil
2010-04-22 19:45 Hans Verkuil
2010-04-21 19:41 Hans Verkuil
2010-04-20 19:41 Hans Verkuil
2010-04-19 19:41 Hans Verkuil
2010-04-18 19:41 Hans Verkuil
2010-04-17 19:37 Hans Verkuil
2010-04-16 19:37 Hans Verkuil
2010-04-15 19:38 Hans Verkuil
2010-04-14 19:38 Hans Verkuil
2010-04-13 19:37 Hans Verkuil
2010-04-12 19:37 Hans Verkuil
2010-04-11 19:41 Hans Verkuil
2010-04-10 19:37 Hans Verkuil
2010-04-09 19:37 Hans Verkuil
2010-04-08 19:29 Hans Verkuil
2010-04-07 19:29 Hans Verkuil
2010-04-06 19:29 Hans Verkuil
2010-04-05 19:39 Hans Verkuil
2010-04-04 19:39 Hans Verkuil
2010-04-03 19:39 Hans Verkuil
2010-04-02 19:38 Hans Verkuil
2010-04-01 19:39 Hans Verkuil
2010-03-31 19:38 Hans Verkuil
2010-03-30 19:38 Hans Verkuil
2010-03-29 19:39 Hans Verkuil
2010-03-28 19:38 Hans Verkuil
2010-03-27 20:38 Hans Verkuil
2010-03-26 20:38 Hans Verkuil
2010-03-25 20:39 Hans Verkuil
2010-03-24 20:37 Hans Verkuil
2010-03-22 20:36 Hans Verkuil
2010-03-21 20:52 Hans Verkuil
2010-03-20 20:36 Hans Verkuil
2010-03-19 20:37 Hans Verkuil
2010-03-15 20:37 Hans Verkuil
2010-03-05 19:52 Hans Verkuil
2010-03-04 19:52 Hans Verkuil
2010-03-03 19:52 Hans Verkuil
2010-01-23 19:59 Hans Verkuil
2010-01-27 20:02 ` Németh Márton
2010-01-27 20:10 ` Hans Verkuil
2009-12-09 19:34 Hans Verkuil
2009-12-08 19:34 Hans Verkuil
2009-12-07 19:34 Hans Verkuil
2009-12-06 19:34 Hans Verkuil
2009-04-13 18:20 Hans Verkuil
2009-04-14 15:13 ` Mauro Carvalho Chehab
2009-04-12 18:21 Hans Verkuil
2009-04-11 18:20 Hans Verkuil
2009-04-10 18:23 Hans Verkuil
2009-04-09 18:20 Hans Verkuil
2009-04-08 22:10 Hans Verkuil
2009-04-08 22:56 ` Miroslav Šustek
2009-04-08 23:11 ` Alexey Klimov
2009-04-08 18:14 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=201003232037.o2NKbUXQ037751@smtp-vbr14.xs4all.nl \
--to=hverkuil@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 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.