From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753948AbcGTK0b (ORCPT ); Wed, 20 Jul 2016 06:26:31 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:53079 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753802AbcGTK03 (ORCPT ); Wed, 20 Jul 2016 06:26:29 -0400 From: Arnd Bergmann To: kernel-build-reports@lists.linaro.org Cc: "Olof's autobuilder" , olof@lixom.net, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, Doug Ledford , gregkh@linuxfoundation.org, linux-media@vger.kernel.org, Mauro Carvalho Chehab , info@kernelci.org Subject: Re: next build: 7 warnings 0 failures (next/next-20160720) Date: Wed, 20 Jul 2016 12:25:48 +0200 Message-ID: <5106658.dbvAtpQNOs@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-28-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <578f4bea.0568620a.1e97.8d17@mx.google.com> References: <578f4bea.0568620a.1e97.8d17@mx.google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:yOKGikyJnht4cBQoQJ02ASN3vLQtiLmlBFlJygytMIzVbiCD3rM mV+r2Fppp4aKUOgcSbFB14DWO1yQ/VqUjpkg/GoVPJNbhOCRLXqtfWqaf41u9Pzs5pSCw2d V2eQ0vh75/2srZSj3UUHwKCCtGxSz83h479IgqSXsAwEURGbgX3N1Gy/mpIUgcP+NhSrQbJ Ur6ZfLVHgbygCGchC2y+Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:kjc6vE9B4HU=:V3Qstcb1qi8/QIaDCWM4km VjthM5XdgIM44+hWhQMAZiGDQwJqRLrN2JecmujvRVF2RgooSIyfFwhqWmihpRwhntpeO7s5q 1NAzLcoVNYKwIsoyAYMuDUh+WC9p79W3p5fbKpiW43fDo2al8X7zKYhThr1YJRZtvwCGbtg08 KBeSUvqLXPYUWdYLvq1nrSTWSMnVZpDaoTBBhOmtwnU0AMwuVPO4Lu/Jve80H4prYVhMOLaM6 rnjMfK2bWvzp8j/GdESGt0xTJOqQi5aeglVGeyGFIAndgFaicviulTA3xhBIkVhKVZRtNZ24B /0hGDyepZX47gRYcutVYLAmUZWFX3uGHATRdqTrBmmHMLPRAuwJZ8PU4d+SWQb4LD56n163Cq nUEDPoQCpAhPLyD0bdbLgDUEQSp9D0dikAYrgGSRmIf4haSzxnAE5iaJ8C5jAACL0ULwvShJl 09B6MpZPo1zCGSV2FSGZTmsUFvDfcj1M1V9OztxQ3+uc2Yt+xrmL2ic4QRyn8vGmgLvoEONqf QZipltpfDvGumfbWn+LRCI9rKJ3AWXZlj57EL3trbY+LqO0ZWD9QfjFEappzRrvVwpgnZnDRr wHra9F58UhsRezoWQx1Q9NeqXVLZA1vJJhtdM1o51mvupWTXT4KvLci40fTaTWvxkkISut37h jw12k/JHfEgKcSlrBFCKDzAvtipjzMJzj4j4osKjxJTzgtPixz2r4N7oz7bNObXBnN5UVT0pW sMMOouoT7j+/CIPy Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, July 20, 2016 3:01:14 AM CEST Olof's autobuilder wrote: > Passed: 122 > Failed: 0 > Warnings: 7 > Section mismatches: 0 Looking pretty good, almost no warnings left. The first one in this list is the only one that already exists in v4.7 (and a long time before that), all other preexisting warnings are fixed in -next. The kernelci autobuilder finds a couple of other warnings on top of these, because they build more unusual configurations and use some slightly older compilers that produce false positives. > Warnings: > 1 drivers/infiniband/core/cma.c:1242:12: warning: 'src_addr_storage.sin_addr.s_addr' may be used uninitialized in this function [-Wmaybe-uninitialized] I sent a patch on July 4 to the infiniband list but got no reply. It only shows up on powerpc, presumably with an older compiler, so I don't consider this as urgent, the only reason to fix it up would be to get to zero warnings for the common architectures. Doug, any chance you can still pick up "infiniband: shut up a maybe-uninitialized warning" for 4.8? > 1 drivers/tty/serial/8250/8250_fintek.c:34:0: warning: "IRQ_MODE" redefined I sent a patch on June 26 to Greg, but he hasn't applied any serial driver patches since June 25, so I assume it's in his queue and will make it into v4.8 without further action on my side. > 2 drivers/media/dvb-frontends/cxd2841er.c:3408:40: warning: 'carrier_offset' may be used uninitialized in this function [-Wmaybe-uninitialized] It's in patchwork, so I assume Mauro will get to it in time: https://patchwork.linuxtv.org/patch/35398/ The warning was introduced by a patch outside of drivers/media in linux-mm ("dynamic_debug: add jump label support"). > 3 drivers/net/wireless/ti/wlcore/spi.c:457:6: warning: unused variable 'ret' [-Wunused-variable] This came up today, and the author of the patch that broke it already sent a fix "wlcore: spi: fix build warning caused by redundant variable". Arnd