From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
stable@kernel.org, Chris.Paterson2@renesas.com
Subject: Re: patch in 4.4.201-rc1 breaks build (mm, meminit: recalculate pcpu batch and high limits after init completes)
Date: Tue, 12 Nov 2019 06:41:04 +0100 [thread overview]
Message-ID: <20191112054104.GA1211223@kroah.com> (raw)
In-Reply-To: <20191111132451.GA1208@duo.ucw.cz>
On Mon, Nov 11, 2019 at 02:24:52PM +0100, Pavel Machek wrote:
> Hi!
>
> This seems to break our build with particular
> .config. (cip-kernel-config/4.4.y-cip/arm/moxa_mxc_defconfig).
>
> commit df82285ab4b974f2040f31dbabdd11e055a282c2
> Author: Mel Gorman <mgorman@techsingularity.net>
> Date: Tue Nov 5 21:16:27 2019 -0800
>
> mm, meminit: recalculate pcpu batch and high limits after init completes
>
> commit 3e8fc0075e24338b1117cdff6a79477427b8dbed upstream.
>
>
>
> Quoting Chris Peterson:
>
> > I've seen a failure this morning with our linux stable-rc build
> > testing.
>
> > Version: 4cb9b88c651a2fff886dd64b6d797343e7ddb4dd Linux 4.4.201-rc1
> > Arch: arm
> > Config: moxa_mxc_defconfig
>
> > Pipeline: https://gitlab.com/cip-playground/linux-stable-rc-ci/pipelines/95016985
> > Failure: https://gitlab.com/cip-playground/linux-stable-rc-ci/pipelines/95016985/failures
> > Log: https://gitlab.com/cip-playground/linux-stable-rc-ci/-/jobs/346974180
> > Config: https://gitlab.com/cip-playground/linux-stable-rc-ci/-/jobs/346974180
>
> > All other configurations that we build were successful.
Sorry, my fault, should now be fixed.
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-12 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 13:24 patch in 4.4.201-rc1 breaks build (mm, meminit: recalculate pcpu batch and high limits after init completes) Pavel Machek
2019-11-12 5:41 ` Greg KH [this message]
2019-11-12 7:22 ` Chris Paterson
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=20191112054104.GA1211223@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Paterson2@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox