From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "kernelci.org bot" <bot@kernelci.org>,
stable <stable@vger.kernel.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Marcin Nowakowski <marcin.nowakowski@imgtec.com>,
Ralf Baechle <ralf@linux-mips.org>,
Sasha Levin <alexander.levin@verizon.com>
Subject: Re: stable-rc/linux-3.18.y build: 170 builds: 4 failed, 166 passed, 4 errors (v3.18.73-36-ge7bfc3a7bb75)
Date: Sat, 7 Oct 2017 11:36:46 +0200 [thread overview]
Message-ID: <20171007093646.GA16840@kroah.com> (raw)
In-Reply-To: <CAK8P3a1x=HAGWHj1x13-YM9VHjh+-bA7Wk-F_i3W3LvUab-WSQ@mail.gmail.com>
On Fri, Oct 06, 2017 at 11:01:36PM +0200, Arnd Bergmann wrote:
> On Fri, Oct 6, 2017 at 9:50 PM, kernelci.org bot <bot@kernelci.org> wrote:
> >
> > stable-rc/linux-3.18.y build: 170 builds: 4 failed, 166 passed, 4 errors (v3.18.73-36-ge7bfc3a7bb75)
> > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.73-36-ge7bfc3a7bb75/
> > Tree: stable-rc
> > Branch: linux-3.18.y
> > Git Describe: v3.18.73-36-ge7bfc3a7bb75
> > Git Commit: e7bfc3a7bb7560487107d3572dc67f8e762acbaf
> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Built: 4 unique architectures
> >
> > Build Failures Detected:
> >
> > mips: gcc version 6.3.0 (GCC)
> > ar7_defconfig FAIL
> > lemote2f_defconfig FAIL
> > loongson3_defconfig FAIL
> > nlm_xlr_defconfig FAIL
> >
> > Errors:
> > arch/mips/kernel/setup.c:588:7: error: implicit declaration of function 'memory_region_available' [-Werror=implicit-function-declaration]
>
> This is caused by c3628230f90f ("MIPS: kexec: Do not reserve
> invalid crashkernel memory on boot"), upstream c3628230f90f3.
>
> The memory_region_available() function was introduced in linux-4.11
> by commit d9b5b658210f ("MIPS: init: Ensure bootmem does not
> corrupt reserved memory"), but this patch has not been backported
> to stable kernels yet.
>
> Right now, the stable-rc trees for 3.18 and 4.9 both have this
> problem, while 4.4 doesn't have a backport of c3628230f90f3
> (yet).
>
> I suppose we either want to have both patches in all stable kernels,
> or drop the c3628230f90f3 backport. Marcin Nowakowski might
> be able to offer some more insight, as he wrote both patches as part
> of a longer patch series. There might be other patches from that
> series that qualify for backports.
Thanks for letting me know, I've now just dropped the MIPS patch from
the trees.
greg k-h
prev parent reply other threads:[~2017-10-07 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59d7de9f.0e941c0a.6a2c9.aa5b@mx.google.com>
2017-10-06 21:01 ` stable-rc/linux-3.18.y build: 170 builds: 4 failed, 166 passed, 4 errors (v3.18.73-36-ge7bfc3a7bb75) Arnd Bergmann
2017-10-07 9:36 ` gregkh [this message]
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=20171007093646.GA16840@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@verizon.com \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=marcin.nowakowski@imgtec.com \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).