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: OK
Date: Sun, 3 Jan 2010 20:50:18 +0100 (CET) [thread overview]
Message-ID: <201001031950.o03JoIjh012466@smtp-vbr4.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: Sun Jan 3 19:00:03 CET 2010
path: http://www.linuxtv.org/hg/v4l-dvb
changeset: 13879:b6b82258cf5e
gcc version: gcc (GCC) 4.3.1
hardware: x86_64
host os: 2.6.26
linux-2.6.30-armv5: OK
linux-2.6.31-armv5: OK
linux-2.6.32-armv5: OK
linux-2.6.33-rc2-armv5: ERRORS
linux-2.6.32-armv5-davinci: OK
linux-2.6.33-rc2-armv5-davinci: ERRORS
linux-2.6.30-armv5-ixp: OK
linux-2.6.31-armv5-ixp: OK
linux-2.6.32-armv5-ixp: OK
linux-2.6.33-rc2-armv5-ixp: ERRORS
linux-2.6.30-armv5-omap2: OK
linux-2.6.31-armv5-omap2: OK
linux-2.6.32-armv5-omap2: OK
linux-2.6.33-rc2-armv5-omap2: ERRORS
linux-2.6.22.19-i686: OK
linux-2.6.23.12-i686: OK
linux-2.6.24.7-i686: OK
linux-2.6.25.11-i686: OK
linux-2.6.26-i686: OK
linux-2.6.27-i686: OK
linux-2.6.28-i686: OK
linux-2.6.29.1-i686: WARNINGS
linux-2.6.30-i686: OK
linux-2.6.31-i686: WARNINGS
linux-2.6.32-i686: WARNINGS
linux-2.6.33-rc2-i686: ERRORS
linux-2.6.30-m32r: OK
linux-2.6.31-m32r: OK
linux-2.6.32-m32r: OK
linux-2.6.33-rc2-m32r: ERRORS
linux-2.6.30-mips: WARNINGS
linux-2.6.31-mips: OK
linux-2.6.32-mips: OK
linux-2.6.33-rc2-mips: ERRORS
linux-2.6.30-powerpc64: WARNINGS
linux-2.6.31-powerpc64: OK
linux-2.6.32-powerpc64: WARNINGS
linux-2.6.33-rc2-powerpc64: ERRORS
linux-2.6.22.19-x86_64: OK
linux-2.6.23.12-x86_64: OK
linux-2.6.24.7-x86_64: OK
linux-2.6.25.11-x86_64: OK
linux-2.6.26-x86_64: OK
linux-2.6.27-x86_64: OK
linux-2.6.28-x86_64: OK
linux-2.6.29.1-x86_64: WARNINGS
linux-2.6.30-x86_64: OK
linux-2.6.31-x86_64: WARNINGS
linux-2.6.32-x86_64: WARNINGS
linux-2.6.33-rc2-x86_64: ERRORS
spec: OK
sparse (linux-2.6.32): ERRORS
sparse (linux-2.6.33-rc2): ERRORS
linux-2.6.16.61-i686: OK
linux-2.6.17.14-i686: OK
linux-2.6.18.8-i686: OK
linux-2.6.19.5-i686: OK
linux-2.6.20.21-i686: OK
linux-2.6.21.7-i686: OK
linux-2.6.16.61-x86_64: OK
linux-2.6.17.14-x86_64: OK
linux-2.6.18.8-x86_64: OK
linux-2.6.19.5-x86_64: OK
linux-2.6.20.21-x86_64: OK
linux-2.6.21.7-x86_64: OK
Detailed results are available here:
http://www.xs4all.nl/~hverkuil/logs/Sunday.log
Full logs are available here:
http://www.xs4all.nl/~hverkuil/logs/Sunday.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-01-03 19:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 19:50 Hans Verkuil [this message]
2010-01-03 20:34 ` [PATCH] rj54n1cb0c: remove compiler warning Németh Márton
2010-01-04 21:01 ` Guennadi Liakhovetski
2010-01-04 21:10 ` Németh Márton
-- strict thread matches above, loose matches on Subject: below --
2010-03-10 20:30 [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: OK Hans Verkuil
2010-03-08 20:05 Hans Verkuil
2010-03-07 20:05 Hans Verkuil
2010-03-06 19:52 Hans Verkuil
2010-03-07 5:49 ` Németh Márton
2010-03-07 9:52 ` Hans Verkuil
2010-03-07 12:20 ` Németh Márton
2010-03-07 12:29 ` Hans Verkuil
2010-03-07 13:00 ` Németh Márton
2010-03-02 19:52 Hans Verkuil
2010-03-01 19:53 Hans Verkuil
2010-01-13 19:58 Hans Verkuil
2010-01-12 19:58 Hans Verkuil
2010-01-11 19:58 Hans Verkuil
2010-01-10 19:58 Hans Verkuil
2010-01-09 19:50 Hans Verkuil
2010-01-08 19:50 Hans Verkuil
2010-01-07 19:50 Hans Verkuil
2010-01-06 19:50 Hans Verkuil
2010-01-05 19:50 Hans Verkuil
2010-01-04 19:50 Hans Verkuil
2010-01-02 19:50 Hans Verkuil
2010-01-01 19:50 Hans Verkuil
2009-12-31 19:50 Hans Verkuil
2009-12-30 19:55 Hans Verkuil
2009-12-29 19:59 Hans Verkuil
2009-12-29 21:21 ` Németh Márton
2009-12-29 22:47 ` Mauro Carvalho Chehab
2009-12-29 23:17 ` Németh Márton
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=201001031950.o03JoIjh012466@smtp-vbr4.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.