linux-kernel - Re: v4.7-rc2 build: 0 failures 5 warnings (v4.7-rc2)

Open Source and information security mailing list archives

Date:	Mon, 06 Jun 2016 11:44:33 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linaro-kernel@...ts.linaro.org
Cc:	Peter Ujfalusi <peter.ujfalusi@...com>,
	Tomi Valkeinen <tomi.valkeinen@...com>,
	Dave Airlie <airlied@...hat.com>,
	kernel-build-reports@...ts.linaro.org,
	dri-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: v4.7-rc2 build: 0 failures 5 warnings (v4.7-rc2)

On Monday, June 6, 2016 2:09:07 AM CEST Build bot for Mark Brown wrote:
> arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
> 
> Warnings:
>         ../drivers/gpu/drm/omapdrm/dss/dsi.c:1170:6: warning: unused variable 'r' [-Wunused-variable]
>         ../drivers/gpu/drm/omapdrm/dss/hdmi5.c:123:6: warning: unused variable 'r' [-Wunused-variable]

These got introduced by Fixes: 973999aa0140 ("drm/omap: Remove
regulator API abuse") in 4.7-rc2, and are trivial to fix, I can provide a
patch if needed.

I also have a couple of other regression fixes in my local tree 
that I hope to see in 4.7, but with DRM I never know when to resend
them, as they sometimes do not show up in linux-next before they get
merged into mainline.

This is my current backlog:

d703eb3c7606 [IN NEXT] drm: sun4i: fix probe error handling
ee0d3dafedb7 [IN NEXT] drm: sun4i: print DMA address correctly
4b51817edcd0 [IN NEXT] drm/sun4i: add COMMON_CLK dependency
04197e0d8201 [SUBMITTED 20160516] drm: exynos: mark pm functions as __maybe_unused
1aa3f513d264 [SUBMITTED 20160516] drm: mediatek: add CONFIG_OF dependency
dee4d1c31214 [SUBMITTED 20160511] drm: mediatek: remove IOMMU_DMA select
845cd86005ea [SUBMITTED 20160511] drm/omap: include linux/of.h where needed
d657e5dd56c5 [SUBMITTED 20160511] drm: mediatek: add COMMON_CLK dependency
539c2a57be6f [SUBMITTED x2 20160225] drm: avoid uninitialized timestamp use in wait_vblank
921b0acae44c [SUBMITTED 2015012drm: armada: use dma_addr_t properly

Am I right to assume that as the first eight that are all regressions against
4.6 will show up in 4.7 without me doing anything further, but that I should
resend the last two so they can make it into 4.8, and get backported if
necessary?

	Arnd
_______________________________________________
Kernel-build-reports mailing list
Kernel-build-reports@...ts.linaro.org
https://lists.linaro.org/mailman/listinfo/kernel-build-reports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives