On Wed, Feb 15, 2017 at 9:02 AM, Olof's autobuilder <build@xxxxxxxxx> wrote: > Here are the build results from automated periodic testing. > > Warnings: 9 It seems we're closing in on zero again, with just two build regressions against 4.10 in linux-next. I did patches for both, and they made it into maintainer trees but not yet into linux-next > Warnings: > > 1 drivers/iio/adc/rcar-gyroadc.c:398:26: warning: 'adcmode' may be used uninitialized in this function [-Wmaybe-uninitialized] > 1 drivers/iio/adc/rcar-gyroadc.c:426:22: warning: 'sample_width' may be used uninitialized in this function [-Wmaybe-uninitialized] > 1 drivers/iio/adc/rcar-gyroadc.c:428:23: warning: 'channels' may be used uninitialized in this function [-Wmaybe-uninitialized] > 1 drivers/iio/adc/rcar-gyroadc.c:429:27: warning: 'num_channels' may be used uninitialized in this function [-Wmaybe-uninitialized] This was "iio: adc: handle unknow of_device_id data", http://lkml.iu.edu/hypermail/linux/kernel/1702.0/02707.html Jonathan applied it into 'fixes-togreg-post-rc1', which is probably enough, though I'd expect that Greg would take it earlier as it addresses a (harmless) regression in -next. > 1 drivers/media/platform/coda/imx-vdoa.c:333:571: warning: passing argument 1 of 'platform_driver_unregister' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] > 1 drivers/media/platform/coda/imx-vdoa.c:333:625: warning: passing argument 1 of 'platform_driver_unregister' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] > 1 drivers/usb/gadget/udc/atmel_usba_udc.c:636:38: warning: 'ept_cfg' may be used uninitialized in this function [-Wmaybe-uninitialized] > 2 drivers/media/platform/coda/imx-vdoa.c:333:181: warning: passing argument 1 of '__platform_driver_register' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] This was "[media] coda/imx-vdoa: platform_driver should not be const", https://patchwork.linuxtv.org/patch/39288/ Hans already marked this as 'merged', so I assume it's on its way in, but just hasn't appeared in linux-next as of today. I think there were a couple of other new build warnings in the kernelci builder, I'll have another look when today's linux-next build results come in from there. Arnd
