All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel-build-reports@lists.linaro.org,
	"kernelci. org bot" <bot@kernelci.org>,
	Oliver O'Halloran <oohall@gmail.com>,
	Anton Blanchard <anton@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable <stable@vger.kernel.org>
Subject: Re: maybe backport to stable: 3b3d7c4 ("mm/init: fix zone boundary creation")
Date: Fri, 13 Jan 2017 11:53:43 +0100	[thread overview]
Message-ID: <20170113105343.GC20965@kroah.com> (raw)
In-Reply-To: <4147313.IZqQRZVWNK@wuerfel>

On Thu, Jan 12, 2017 at 03:50:01PM +0100, Arnd Bergmann wrote:
> On Thursday, January 12, 2017 6:07:25 AM CET kernelci. org bot wrote:
> > stable build: 199 builds: 1 failed, 198 passed, 68 warnings (v4.4.42)
> > 
> 
> Things are looking much better already, and I found one upstream
> patch (from v4.8) that fixes more than half of the remaining MIPS and
> x86 warnings on linux-4.4-stable:
> 
> > mips:    gcc version 6.3.0 (GCC)
> > 
> >     allnoconfig: 1 warning
> >     ar7_defconfig: 2 warnings
> >     ath79_defconfig: 1 warning
> >     bcm47xx_defconfig: 1 warning
> >     bcm63xx_defconfig: 1 warning
> >     capcella_defconfig: 2 warnings
> >     ci20_defconfig: 1 warning
> >     cobalt_defconfig: 1 warning
> >     db1xxx_defconfig: 1 warning
> >     decstation_defconfig: 4 warnings
> >     defconfig+CONFIG_LKDTM=y: 2 warnings
> >     e55_defconfig: 1 warning
> >     fuloong2e_defconfig: 1 warning
> >     gpr_defconfig: 2 warnings
> >     ip22_defconfig: 2 warnings
> >     ip27_defconfig: 2 warnings
> >     ip32_defconfig: 1 warning
> >     jazz_defconfig: 1 warning
> >     jmr3927_defconfig: 1 warning
> >     lasat_defconfig: 1 warning
> >     lemote2f_defconfig: 2 warnings
> >     loongson3_defconfig: 2 warnings
> >     ls1b_defconfig: 1 warning
> >     markeins_defconfig: 1 warning
> >     mips_paravirt_defconfig: 1 warning
> >     mpc30x_defconfig: 1 warning
> >     msp71xx_defconfig: 2 warnings
> >     mtx1_defconfig: 2 warnings
> >     nlm_xlp_defconfig: 4 warnings
> >     nlm_xlr_defconfig: 3 warnings
> >     pistachio_defconfig: 1 warning
> >     pnx8335_stb225_defconfig: 1 warning
> >     qi_lb60_defconfig: 1 warning
> >     rb532_defconfig: 1 warning
> >     rbtx49xx_defconfig: 1 warning
> >     rm200_defconfig: 1 warning
> >     rt305x_defconfig: 4 warnings
> >     sead3_defconfig: 1 warning
> >     sead3micro_defconfig: 1 warning
> >     tb0219_defconfig: 1 warning
> >     tb0226_defconfig: 1 warning
> >     tb0287_defconfig: 1 warning
> >     tinyconfig: 1 warning
> >     workpad_defconfig: 1 warning
> >     xilfpga_defconfig: 1 warning
> >     xway_defconfig: 1 warning
> > 
> > x86:    gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
> > 
> >     tinyconfig: 1 warning
> > 
> > Warnings summary:
> > 
> >      41  mm/page_alloc.c:5705:34: warning: array subscript is below array bounds [-Warray-bounds]
> 
> I don't understand that patch enough to say if it is appropriate
> for a backport, but it applies cleanly on v4.4 and fixes the warning. 
> Adding everyone who was involved so they can comment.

It looks valid to me, so I've now queued it up, thanks.

greg k-h

  reply	other threads:[~2017-01-13 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58778d9d.08301c0a.bb8d8.2c60@mx.google.com>
2017-01-12 14:50 ` maybe backport to stable: 3b3d7c4 ("mm/init: fix zone boundary creation") Arnd Bergmann
2017-01-13 10:53   ` Greg KH [this message]
2017-01-18  0:21   ` Oliver O'Halloran

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=20170113105343.GC20965@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=bot@kernelci.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=mgorman@techsingularity.net \
    --cc=oohall@gmail.com \
    --cc=paulus@samba.org \
    --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.