Re: cron job: media_tree daily build: OK

2018-05-13 Thread Hans Verkuil 
Great to see an OK here! And it's going to change to warnings for the
next build: I've updated the compiler to gcc-8.1.

A quick look at the warnings shows mostly warnings of this type:

warning: '__builtin_strncpy' output truncated copying 15 bytes from a string of 
length 17 [-Wstringop-truncation]

In most cases the strncpy should really be replaced with strlcpy.

Compiling with gcc 8.1 give a truckload of objtool warnings. For the time
being I've added a grep -v to ignore all of them. It looks like objtool isn't
quite gcc 8 compatible.

Regards,

Hans

On 05/13/2018 07:09 AM, Hans Verkuil wrote:
> This message is generated daily by a cron job that builds media_tree for
> the kernels and architectures in the list below.
> 
> Results of the daily build of media_tree:
> 
> date: Sun May 13 05:00:14 CEST 2018
> media-tree git hash:  2a5f2705c97625aa1a4e1dd4d584eaa05392e060
> media_build git hash: d72556c0502c096c089c99c58ee4a02a13133361
> v4l-utils git hash:   51cfcefe65225430fd6794301adcaae133ebfc2d
> gcc version:  i686-linux-gcc (GCC) 7.3.0
> sparse version:   0.5.2-RC1
> smatch version:   0.5.1
> host hardware:x86_64
> host os:  4.15.0-3-amd64
> 
> linux-git-arm-at91: OK
> linux-git-arm-davinci: OK
> linux-git-arm-multi: OK
> linux-git-arm-pxa: OK
> linux-git-arm-stm32: OK
> linux-git-arm64: OK
> linux-git-i686: OK
> linux-git-mips: OK
> linux-git-powerpc64: OK
> linux-git-sh: OK
> linux-git-x86_64: OK
> Check COMPILE_TEST: OK
> linux-2.6.36.4-i686: OK
> linux-2.6.36.4-x86_64: OK
> linux-2.6.37.6-i686: OK
> linux-2.6.37.6-x86_64: OK
> linux-2.6.38.8-i686: OK
> linux-2.6.38.8-x86_64: OK
> linux-2.6.39.4-i686: OK
> linux-2.6.39.4-x86_64: OK
> linux-3.0.101-i686: OK
> linux-3.0.101-x86_64: OK
> linux-3.1.10-i686: OK
> linux-3.1.10-x86_64: OK
> linux-3.2.101-i686: OK
> linux-3.2.101-x86_64: OK
> linux-3.3.8-i686: OK
> linux-3.3.8-x86_64: OK
> linux-3.4.113-i686: OK
> linux-3.4.113-x86_64: OK
> linux-3.5.7-i686: OK
> linux-3.5.7-x86_64: OK
> linux-3.6.11-i686: OK
> linux-3.6.11-x86_64: OK
> linux-3.7.10-i686: OK
> linux-3.7.10-x86_64: OK
> linux-3.8.13-i686: OK
> linux-3.8.13-x86_64: OK
> linux-3.9.11-i686: OK
> linux-3.9.11-x86_64: OK
> linux-3.10.108-i686: OK
> linux-3.10.108-x86_64: OK
> linux-3.11.10-i686: OK
> linux-3.11.10-x86_64: OK
> linux-3.12.74-i686: OK
> linux-3.12.74-x86_64: OK
> linux-3.13.11-i686: OK
> linux-3.13.11-x86_64: OK
> linux-3.14.79-i686: OK
> linux-3.14.79-x86_64: OK
> linux-3.15.10-i686: OK
> linux-3.15.10-x86_64: OK
> linux-3.16.56-i686: OK
> linux-3.16.56-x86_64: OK
> linux-3.17.8-i686: OK
> linux-3.17.8-x86_64: OK
> linux-3.18.102-i686: OK
> linux-3.18.102-x86_64: OK
> linux-3.19.8-i686: OK
> linux-3.19.8-x86_64: OK
> linux-4.0.9-i686: OK
> linux-4.0.9-x86_64: OK
> linux-4.1.51-i686: OK
> linux-4.1.51-x86_64: OK
> linux-4.2.8-i686: OK
> linux-4.2.8-x86_64: OK
> linux-4.3.6-i686: OK
> linux-4.3.6-x86_64: OK
> linux-4.4.109-i686: OK
> linux-4.4.109-x86_64: OK
> linux-4.5.7-i686: OK
> linux-4.5.7-x86_64: OK
> linux-4.6.7-i686: OK
> linux-4.6.7-x86_64: OK
> linux-4.7.10-i686: OK
> linux-4.7.10-x86_64: OK
> linux-4.8.17-i686: OK
> linux-4.8.17-x86_64: OK
> linux-4.9.91-i686: OK
> linux-4.9.91-x86_64: OK
> linux-4.10.17-i686: OK
> linux-4.10.17-x86_64: OK
> linux-4.11.12-i686: OK
> linux-4.11.12-x86_64: OK
> linux-4.12.14-i686: OK
> linux-4.12.14-x86_64: OK
> linux-4.13.16-i686: OK
> linux-4.13.16-x86_64: OK
> linux-4.14.31-i686: OK
> linux-4.14.31-x86_64: OK
> linux-4.15.14-i686: OK
> linux-4.15.14-x86_64: OK
> linux-4.16.8-i686: OK
> linux-4.16.8-x86_64: OK
> linux-4.17-rc4-i686: OK
> linux-4.17-rc4-x86_64: OK
> apps: OK
> spec-git: OK
> sparse: WARNINGS
> 
> 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 Media Infrastructure API from this daily build is here:
> 
> http://www.xs4all.nl/~hverkuil/spec/index.html
>

Re: cron job: media_tree daily build: OK

2018-04-04 Thread Hans Verkuil 
On 04/04/18 13:15, Mauro Carvalho Chehab wrote:
> Hi Hans,
> 
> Em Wed, 04 Apr 2018 05:45:22 +0200
> "Hans Verkuil"  escreveu:
> 
> Not sure what versions of sparse/smatch you're using. Here, I'm using the
> latest version from both trees. Anyway, I'm getting different results
> than you (both built for i386).

My sparse version was out of date, my smatch version is the same as yours.

I've fixed the sparse version for the build.

Regards,

Hans

> 
>> sparse: WARNINGS
> 
> The only sparse warnings I'm getting here are at ddbridge driver:
> 
> $ make ARCH=i386  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 
> W=1 CHECK='/devel/sparse/sparse' M=drivers/media
> drivers/media/pci/ddbridge/ddbridge-core.c:442:9: warning: context imbalance 
> in 'ddb_output_start' - different lock contexts for basic block
> drivers/media/pci/ddbridge/ddbridge-core.c:457:9: warning: context imbalance 
> in 'ddb_output_stop' - different lock contexts for basic block
> drivers/media/pci/ddbridge/ddbridge-core.c:472:9: warning: context imbalance 
> in 'ddb_input_stop' - different lock contexts for basic block
> drivers/media/pci/ddbridge/ddbridge-core.c:504:9: warning: context imbalance 
> in 'ddb_input_start' - different lock contexts for basic block
> 
> My sparse tree is at this commit:
> 
> commit d1c2f8d3d4205ca1ae7cf0ec2cbd89a7fce73e5c (HEAD -> master, tag: 
> v0.5.2-rc1, origin/master, origin/HEAD)
> Author: Luc Van Oostenryck 
> Date:   Fri Mar 2 21:58:57 2018 +0100
> 
> bump up version to 0.5.2-RC1
> 
> Signed-off-by: Luc Van Oostenryck 
> Signed-off-by: Christopher Li 
> 
>> smatch: OK
> 
> Also here, my results are different. There are still a few smatch warnings
> there:
> 
> $ make ARCH=i386  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 
> W=1 CHECK='/devel/smatch/smatch -p=kernel' M=drivers/media
> drivers/media/v4l2-core/v4l2-fwnode.c:832 
> v4l2_fwnode_reference_parse_int_props() warn: passing zero to 'PTR_ERR'
> drivers/media/dvb-core/dvb_frontend.c:314 dvb_frontend_get_event() warn: 
> inconsistent returns 'sem:>sem'.
>   Locked on:   line 288
>line 295
>line 306
>line 314
>   Unlocked on: line 303
> drivers/media/usb/dvb-usb-v2/lmedm04.c:742 lme_firmware_switch() warn: 
> missing break? reassigning '*fw_lme'
> drivers/media/usb/dvb-usb-v2/lmedm04.c:765 lme_firmware_switch() warn: 
> missing break? reassigning '*fw_lme'
> drivers/media/rc/st_rc.c:110 st_rc_rx_interrupt() warn: this loop depends on 
> readl() succeeding
> drivers/media/pci/mantis/mantis_uart.c:105 mantis_uart_work() warn: this loop 
> depends on readl() succeeding
> drivers/media/tuners/r820t.c:2374 r820t_attach() error: potential null 
> dereference 'priv'.  (kzalloc returns null)
> drivers/media/platform/vsp1/vsp1_wpf.c:456 wpf_configure() error: we 
> previously assumed 'pipe->bru' could be null (see line 455)
> 
> With regards to those remaining warnings:
> 
> 1) There's a fix already for the vsp1_wpf warning that I merged today
>on my fixes tree, to be sent for 4.17-rc1.
> 2) The two missing breaks are false positive. As discussed with Dan,
>maybe the best here is to change the logic at smatch, as the
>code there is correct.
> 
> I am at this commit:
> 
> commit 3b5bf5c91fe648f89c12dfeb4cda3fe36e7f19c5 (origin/master, origin/HEAD)
> Author: Dan Carpenter 
> Date:   Mon Mar 26 15:13:22 2018 +0300
> 
> implied: improve handling of assignments in arguments
> 
> This example code wasn't parsed correctly:
> 
> if (IS_ERR(ptr = some_function())) {
> 
> We should say basically use "ptr" as the implied arg instead of the
> assignment expression.
> 
> Reported-by: Mauro Carvalho Chehab 
> Signed-off-by: Dan Carpenter 
> 
> I added an extra patch to prevent some other warnings due to very big
> functions:
> 
> commit 735d5595e2c23abc544858109925941f4b14f4a0
> Author: Mauro Carvalho Chehab 
> Date:   Fri Jun 5 09:49:00 2015 -0300
> 
> smatch_slist: use a higher memory limit
> 
> 50M is not enough for some code at the Kernel. It produces this
> warning:
> 
> drivers/media/pci/cx23885/cx23885-dvb.c:2046 dvb_register() Function too 
> hairy.  Giving up.
> 
> While checking for troubles on a loop with attaches the device
> specific sub-devices based on the PCI ID.
> 
> There's not much that could be done at the code to simplify it.
> The code there is big just because the cx23885 driver supports
> lots of different cards.
> 
> On the other hand, increasing the maximum memory size to 500MB
> is cheap, as nowadays even desktops have 16GB.
> 
> So, let's increase it.
> 
> Signed-off-by: Mauro Carvalho Chehab

Re: cron job: media_tree daily build: OK

2018-04-04 Thread Mauro Carvalho Chehab 
Hi Hans,

Em Wed, 04 Apr 2018 05:45:22 +0200
"Hans Verkuil"  escreveu:

Not sure what versions of sparse/smatch you're using. Here, I'm using the
latest version from both trees. Anyway, I'm getting different results
than you (both built for i386).

> sparse: WARNINGS

The only sparse warnings I'm getting here are at ddbridge driver:

$ make ARCH=i386  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 W=1 
CHECK='/devel/sparse/sparse' M=drivers/media
drivers/media/pci/ddbridge/ddbridge-core.c:442:9: warning: context imbalance in 
'ddb_output_start' - different lock contexts for basic block
drivers/media/pci/ddbridge/ddbridge-core.c:457:9: warning: context imbalance in 
'ddb_output_stop' - different lock contexts for basic block
drivers/media/pci/ddbridge/ddbridge-core.c:472:9: warning: context imbalance in 
'ddb_input_stop' - different lock contexts for basic block
drivers/media/pci/ddbridge/ddbridge-core.c:504:9: warning: context imbalance in 
'ddb_input_start' - different lock contexts for basic block

My sparse tree is at this commit:

commit d1c2f8d3d4205ca1ae7cf0ec2cbd89a7fce73e5c (HEAD -> master, tag: 
v0.5.2-rc1, origin/master, origin/HEAD)
Author: Luc Van Oostenryck 
Date:   Fri Mar 2 21:58:57 2018 +0100

bump up version to 0.5.2-RC1

Signed-off-by: Luc Van Oostenryck 
Signed-off-by: Christopher Li 

> smatch: OK

Also here, my results are different. There are still a few smatch warnings
there:

$ make ARCH=i386  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 W=1 
CHECK='/devel/smatch/smatch -p=kernel' M=drivers/media
drivers/media/v4l2-core/v4l2-fwnode.c:832 
v4l2_fwnode_reference_parse_int_props() warn: passing zero to 'PTR_ERR'
drivers/media/dvb-core/dvb_frontend.c:314 dvb_frontend_get_event() warn: 
inconsistent returns 'sem:>sem'.
  Locked on:   line 288
   line 295
   line 306
   line 314
  Unlocked on: line 303
drivers/media/usb/dvb-usb-v2/lmedm04.c:742 lme_firmware_switch() warn: missing 
break? reassigning '*fw_lme'
drivers/media/usb/dvb-usb-v2/lmedm04.c:765 lme_firmware_switch() warn: missing 
break? reassigning '*fw_lme'
drivers/media/rc/st_rc.c:110 st_rc_rx_interrupt() warn: this loop depends on 
readl() succeeding
drivers/media/pci/mantis/mantis_uart.c:105 mantis_uart_work() warn: this loop 
depends on readl() succeeding
drivers/media/tuners/r820t.c:2374 r820t_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/platform/vsp1/vsp1_wpf.c:456 wpf_configure() error: we previously 
assumed 'pipe->bru' could be null (see line 455)

With regards to those remaining warnings:

1) There's a fix already for the vsp1_wpf warning that I merged today
   on my fixes tree, to be sent for 4.17-rc1.
2) The two missing breaks are false positive. As discussed with Dan,
   maybe the best here is to change the logic at smatch, as the
   code there is correct.

I am at this commit:

commit 3b5bf5c91fe648f89c12dfeb4cda3fe36e7f19c5 (origin/master, origin/HEAD)
Author: Dan Carpenter 
Date:   Mon Mar 26 15:13:22 2018 +0300

implied: improve handling of assignments in arguments

This example code wasn't parsed correctly:

if (IS_ERR(ptr = some_function())) {

We should say basically use "ptr" as the implied arg instead of the
assignment expression.

Reported-by: Mauro Carvalho Chehab 
Signed-off-by: Dan Carpenter 

I added an extra patch to prevent some other warnings due to very big
functions:

commit 735d5595e2c23abc544858109925941f4b14f4a0
Author: Mauro Carvalho Chehab 
Date:   Fri Jun 5 09:49:00 2015 -0300

smatch_slist: use a higher memory limit

50M is not enough for some code at the Kernel. It produces this
warning:

drivers/media/pci/cx23885/cx23885-dvb.c:2046 dvb_register() Function too 
hairy.  Giving up.

While checking for troubles on a loop with attaches the device
specific sub-devices based on the PCI ID.

There's not much that could be done at the code to simplify it.
The code there is big just because the cx23885 driver supports
lots of different cards.

On the other hand, increasing the maximum memory size to 500MB
is cheap, as nowadays even desktops have 16GB.

So, let's increase it.

Signed-off-by: Mauro Carvalho Chehab 
Signed-off-by: Mauro Carvalho Chehab 

diff --git a/smatch_flow.c b/smatch_flow.c
index 94a1c6b5dd89..a7bdd210b904 100644
--- a/smatch_flow.c
+++ b/smatch_flow.c
@@ -982,8 +982,7 @@ void __split_stmt(struct statement *stmt)
 
__bail_on_rest_of_function = 1;
final_pass = 1;
-   sm_msg("Function too hairy.  Giving up. %lu seconds",
-

Re: cron job: media_tree daily build: OK

2016-03-21 Thread Hans Verkuil 
On 03/21/2016 10:57 AM, Mauro Carvalho Chehab wrote:
> Em Mon, 21 Mar 2016 05:05:07 +0100
> "Hans Verkuil"  escreveu:
> 
>> This message is generated daily by a cron job that builds media_tree for
>> the kernels and architectures in the list below.
>>
>> Results of the daily build of media_tree:
>>
>> date:Mon Mar 21 04:00:22 CET 2016
>> git branch:  test
>> git hash:b39950960d2b890c21465c69c7c0e4ff6253c6b5
>> gcc version: i686-linux-gcc (GCC) 5.3.0
>> sparse version:  v0.5.0-56-g7647c77
>> smatch version:  Warning: /share/smatch/smatch_data/ is not accessible.
>> Use --no-data or --data to suppress this message.
>> v0.5.0-3353-gcae47da
> 
> Not sure how you're running smatch, but what I do here is to run
> it as:
>   //smatch
> 
> This way, it finds the smatch_data dir at / suppress several false positive error messages from the smatch logs.
> 
> As a side effect, it simplifies a little bit the procedure to update
> smatch's version.

It was a botched smatch install. It should be OK for the next build.

Thanks for noticing this!

Hans

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: cron job: media_tree daily build: OK

2016-03-21 Thread Mauro Carvalho Chehab 
Em Mon, 21 Mar 2016 06:57:08 -0300
Mauro Carvalho Chehab  escreveu:

> Em Mon, 21 Mar 2016 05:05:07 +0100
> "Hans Verkuil"  escreveu:
> 
> > This message is generated daily by a cron job that builds media_tree for
> > the kernels and architectures in the list below.
> > 
> > Results of the daily build of media_tree:
> > 
> > date:   Mon Mar 21 04:00:22 CET 2016
> > git branch: test
> > git hash:   b39950960d2b890c21465c69c7c0e4ff6253c6b5
> > gcc version:i686-linux-gcc (GCC) 5.3.0
> > sparse version: v0.5.0-56-g7647c77
> > smatch version: Warning: /share/smatch/smatch_data/ is not accessible.
> > Use --no-data or --data to suppress this message.
> > v0.5.0-3353-gcae47da  
> 
> Not sure how you're running smatch, but what I do here is to run
> it as:
>   //smatch
> 
> This way, it finds the smatch_data dir at / suppress several false positive error messages from the smatch logs.
> 
> As a side effect, it simplifies a little bit the procedure to update
> smatch's version.
> 
> Regards

As a reference, those are what I get here with the latest version of
smatch (plus a patch to avoid a "Function too hairy." warning, posted
in the end of this email):

$ make ARCH=i386  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 W=1 
CHECK='/devel/smatch/smatch -p=kernel' M=drivers/staging/media
$ make ARCH=i386  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 W=1 
CHECK='/devel/smatch/smatch -p=kernel' M=drivers/media
drivers/media/tuners/tuner-xc2028.c:1498 xc2028_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/radio/radio-aztech.c:87 aztech_alloc() warn: possible memory leak 
of 'az'
drivers/media/pci/mantis/mantis_uart.c:105 mantis_uart_work() warn: this loop 
depends on readl() succeeding
drivers/media/dvb-core/dvb_frontend.c:272 dvb_frontend_get_event() warn: 
inconsistent returns 'sem:>sem'.
  Locked on:   line 246
   line 253
   line 264
   line 272
  Unlocked on: line 261
drivers/media/pci/ddbridge/ddbridge-core.c:1007 input_tasklet() warn: this loop 
depends on readl() succeeding
drivers/media/pci/ddbridge/ddbridge-core.c:1351 flashio() warn: this loop 
depends on readl() succeeding
drivers/media/pci/ddbridge/ddbridge-core.c:1371 flashio() warn: this loop 
depends on readl() succeeding
drivers/media/tuners/tuner-simple.c:1102 simple_tuner_attach() error: potential 
null dereference 'priv'.  (kzalloc returns null)
drivers/media/radio/radio-typhoon.c:79 typhoon_alloc() warn: possible memory 
leak of 'ty'
drivers/media/radio/radio-aimslab.c:73 rtrack_alloc() warn: possible memory 
leak of 'rt'
drivers/media/radio/radio-zoltrix.c:83 zoltrix_alloc() warn: possible memory 
leak of 'zol'
drivers/media/radio/radio-gemtek.c:189 gemtek_alloc() warn: possible memory 
leak of 'gt'
drivers/media/tuners/tda9887.c:692 tda9887_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/radio/radio-trust.c:60 trust_alloc() warn: possible memory leak 
of 'tr'
drivers/media/tuners/tda18271-fe.c:1317 tda18271_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/tuners/xc5000.c:1418 xc5000_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/tuners/xc4000.c:1690 xc4000_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/tuners/mxl5007t.c:878 mxl5007t_attach() error: potential null 
dereference 'state'.  (kzalloc returns null)
drivers/media/rc/ir-lirc-codec.c:289 ir_lirc_ioctl() warn: check for integer 
overflow 'val'
drivers/media/tuners/r820t.c:2342 r820t_attach() error: potential null 
dereference 'priv'.  (kzalloc returns null)
drivers/media/rc/st_rc.c:110 st_rc_rx_interrupt() warn: this loop depends on 
readl() succeeding
drivers/media/pci/bt8xx/dvb-bt8xx.c:720 frontend_init() warn: possible memory 
leak of 'state'
./arch/x86/include/asm/bitops.h:416:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:416:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:457:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:457:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:457:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:457:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:457:22: warning: asm output is not an lvalue
./arch/x86/include/asm/bitops.h:457:22: warning: asm output is not an lvalue
drivers/media/usb/uvc/uvc_ctrl.c:1387 uvc_ctrl_begin() warn: inconsistent 
returns 'mutex:>ctrl_mutex'.
  Locked on:   line 1387
  Unlocked on: line 1387
drivers/media/usb/pvrusb2/pvrusb2-hdw.c:3676 pvr2_send_request_ex() error: we 
previously assumed 'write_data' could be null (see line 3648)
drivers/media/usb/pvrusb2/pvrusb2-hdw.c:3829 pvr2_send_request_ex() error: we

Re: cron job: media_tree daily build: OK

2016-03-21 Thread Mauro Carvalho Chehab 
Em Mon, 21 Mar 2016 05:05:07 +0100
"Hans Verkuil"  escreveu:

> This message is generated daily by a cron job that builds media_tree for
> the kernels and architectures in the list below.
> 
> Results of the daily build of media_tree:
> 
> date: Mon Mar 21 04:00:22 CET 2016
> git branch:   test
> git hash: b39950960d2b890c21465c69c7c0e4ff6253c6b5
> gcc version:  i686-linux-gcc (GCC) 5.3.0
> sparse version:   v0.5.0-56-g7647c77
> smatch version:   Warning: /share/smatch/smatch_data/ is not accessible.
> Use --no-data or --data to suppress this message.
> v0.5.0-3353-gcae47da

Not sure how you're running smatch, but what I do here is to run
it as:
//smatch

This way, it finds the smatch_data dir at /

Re: cron job: media_tree daily build: OK

2013-11-25 Thread Hans Verkuil 
Finally! It's producing an OK result. It's been a long, long time since we
managed that.

Next step: continue whittling away at the sparse warnings/errors.

Regards,

Hans

On 11/25/2013 04:32 AM, Hans Verkuil wrote:
 This message is generated daily by a cron job that builds media_tree for
 the kernels and architectures in the list below.
 
 Results of the daily build of media_tree:
 
 date: Mon Nov 25 04:00:27 CET 2013
 git branch:   test
 git hash: 80f93c7b0f4599ffbdac8d964ecd1162b8b618b9
 gcc version:  i686-linux-gcc (GCC) 4.8.1
 sparse version:   0.4.5-rc1
 host hardware:x86_64
 host os:  3.12-0.slh.2-amd64
 
 linux-git-arm-at91: OK
 linux-git-arm-davinci: OK
 linux-git-arm-exynos: OK
 linux-git-arm-mx: OK
 linux-git-arm-omap: OK
 linux-git-arm-omap1: OK
 linux-git-arm-pxa: OK
 linux-git-blackfin: OK
 linux-git-i686: OK
 linux-git-m32r: OK
 linux-git-mips: OK
 linux-git-powerpc64: OK
 linux-git-sh: OK
 linux-git-x86_64: OK
 linux-2.6.31.14-i686: OK
 linux-2.6.32.27-i686: OK
 linux-2.6.33.7-i686: OK
 linux-2.6.34.7-i686: OK
 linux-2.6.35.9-i686: OK
 linux-2.6.36.4-i686: OK
 linux-2.6.37.6-i686: OK
 linux-2.6.38.8-i686: OK
 linux-2.6.39.4-i686: OK
 linux-3.0.60-i686: OK
 linux-3.1.10-i686: OK
 linux-3.2.37-i686: OK
 linux-3.3.8-i686: OK
 linux-3.4.27-i686: OK
 linux-3.5.7-i686: OK
 linux-3.6.11-i686: OK
 linux-3.7.4-i686: OK
 linux-3.8-i686: OK
 linux-3.9.2-i686: OK
 linux-3.10.1-i686: OK
 linux-3.11.1-i686: OK
 linux-3.12-i686: OK
 linux-2.6.31.14-x86_64: OK
 linux-2.6.32.27-x86_64: OK
 linux-2.6.33.7-x86_64: OK
 linux-2.6.34.7-x86_64: OK
 linux-2.6.35.9-x86_64: OK
 linux-2.6.36.4-x86_64: OK
 linux-2.6.37.6-x86_64: OK
 linux-2.6.38.8-x86_64: OK
 linux-2.6.39.4-x86_64: OK
 linux-3.0.60-x86_64: OK
 linux-3.1.10-x86_64: OK
 linux-3.2.37-x86_64: OK
 linux-3.3.8-x86_64: OK
 linux-3.4.27-x86_64: OK
 linux-3.5.7-x86_64: OK
 linux-3.6.11-x86_64: OK
 linux-3.7.4-x86_64: OK
 linux-3.8-x86_64: OK
 linux-3.9.2-x86_64: OK
 linux-3.10.1-x86_64: OK
 linux-3.11.1-x86_64: OK
 linux-3.12-x86_64: OK
 apps: OK
 spec-git: OK
 sparse version:   0.4.5-rc1
 sparse: ERRORS
 
 Detailed results are available here:
 
 http://www.xs4all.nl/~hverkuil/logs/Monday.log
 
 Full logs are available here:
 
 http://www.xs4all.nl/~hverkuil/logs/Monday.tar.bz2
 
 The Media Infrastructure API from this daily build is here:
 
 http://www.xs4all.nl/~hverkuil/spec/media.html
 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
 

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html