From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752763AbdJFJXd (ORCPT ); Fri, 6 Oct 2017 05:23:33 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:51010 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751846AbdJFJXa (ORCPT ); Fri, 6 Oct 2017 05:23:30 -0400 Date: Fri, 6 Oct 2017 11:23:37 +0200 From: gregkh To: Arnd Bergmann Cc: "Olof's autobuilder" , stable , Linux Kernel Mailing List , Olof Johansson , Kernel Build Reports Mailman List Subject: Re: stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae) Message-ID: <20171006092337.GC17988@kroah.com> References: <59d381d0.032e620a.7f81d.7320@mx.google.com> <20171005091649.GC26886@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 06, 2017 at 11:12:32AM +0200, Arnd Bergmann wrote: > On Thu, Oct 5, 2017 at 11:16 AM, gregkh wrote: > > On Wed, Oct 04, 2017 at 09:31:25PM +0200, Arnd Bergmann wrote: > >> On Tue, Oct 3, 2017 at 2:25 PM, Olof's autobuilder wrote: > >> > >> > Warnings: > >> > > >> > 2 drivers/media/pci/ttpci/av7110_hw.h:406:3: warning: 'memcpy': specified size between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] > >> > >> This was fixed in linux-4.11: > >> > >> 69d3973af1ac ("[media] ttpci: address stringop overflow warning") > >> > >> > 4 drivers/staging/nvec/nvec_ps2.c:168:14: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] > >> > >> and this was fixed in linux-4.2: > >> > >> 716baa7b430c ("staging: nvec: remove duplicated const") > >> > >> Both warnings show up for Olof's build bot in 3.18, but the fixes should > >> also apply to the later kernels. > > > > Thanks for these, all now queued up. > > It looks like you applied them to 4.4.y and 4.9.y, but not to 3.18.y, which > still shows both problems in the 3.18.73 build report. > > Can you check again? I see them in my patch queue, where are you looking? Let me push out the next 3.18.y-rc release so you can check easier... thanks, greg k-h