From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Olof's autobuilder" <build@lixom.net>,
stable <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>
Subject: Re: stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae)
Date: Fri, 6 Oct 2017 11:23:37 +0200 [thread overview]
Message-ID: <20171006092337.GC17988@kroah.com> (raw)
In-Reply-To: <CAK8P3a2_=bBP1cyoSgU9PvFs_iUhofbFoOjMMU0tD3o=dV6F_g@mail.gmail.com>
On Fri, Oct 06, 2017 at 11:12:32AM +0200, Arnd Bergmann wrote:
> On Thu, Oct 5, 2017 at 11:16 AM, gregkh <gregkh@linuxfoundation.org> 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 <build@lixom.net> 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
next prev parent reply other threads:[~2017-10-06 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59d381d0.032e620a.7f81d.7320@mx.google.com>
2017-10-04 19:31 ` stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae) Arnd Bergmann
2017-10-05 9:16 ` gregkh
2017-10-06 9:12 ` Arnd Bergmann
2017-10-06 9:23 ` gregkh [this message]
2017-10-06 9:47 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171006092337.GC17988@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.