From: Marcin Nowakowski <marcin.nowakowski@mips.com>
To: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
Sasha Levin <alexander.levin@verizon.com>,
Marcin Nowakowski <marcin.nowakowski@imgtec.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: Fwd: stable-rc/linux-4.4.y build: 182 builds: 60 failed, 122 passed, 60 errors, 60 warnings (v4.4.99-60-g803704b287d8)
Date: Mon, 20 Nov 2017 10:41:24 +0100 [thread overview]
Message-ID: <8a278610-716d-321e-a403-6c8e74b05c82@mips.com> (raw)
In-Reply-To: <CAK8P3a1TCQR1gDRL_Ns5tTJyj8x_NJupM74i8rKpUZ0hRa1mcQ@mail.gmail.com>
Hi Arnd, Greg,
On 19.11.2017 21:55, Arnd Bergmann wrote:
> [Adding the others to cc]
>
> ---------- Forwarded message ----------
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Sun, Nov 19, 2017 at 9:53 PM
> Subject: Re: stable-rc/linux-4.4.y build: 182 builds: 60 failed, 122
> passed, 60 errors, 60 warnings (v4.4.99-60-g803704b287d8)
> To: "kernelci.org bot" <bot@kernelci.org>, gregkh <gregkh@linuxfoundation.org>
> Cc: Tom Gall <tom.gall@linaro.org>, Sumit Semwal
> <sumit.semwal@linaro.org>, Amit Pundir <amit.pundir@linaro.org>, Arnd
> Bergmann <arnd.bergmann@linaro.org>, Anmar Oueja
> <anmar.oueja@linaro.org>
>
>
> On Sun, Nov 19, 2017 at 5:35 PM, kernelci.org bot <bot@kernelci.org> wrote:
>> stable-rc/linux-4.4.y build: 182 builds: 60 failed, 122 passed, 60 errors, 60 warnings (v4.4.99-60-g803704b287d8)
>>
>> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.99-60-g803704b287d8/
>>
>> Tree: stable-rc
>> Branch: linux-4.4.y
>> Git Describe: v4.4.99-60-g803704b287d8
>> Git Commit: 803704b287d89efcd70fade9e650176282a1d766
>> 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)
>>
>> allnoconfig: FAIL
>> ar7_defconfig: FAIL
>> ath79_defconfig: FAIL
>> bcm47xx_defconfig: FAIL
>> ...
>>
>> Errors summary:
>>
>> 60 arch/mips/kernel/setup.c:439:8: error: implicit declaration of function 'PHYS_PFN' [-Werror=implicit-function-declaration]
>
> All mips builds failed with this error, apparently caused by the
> backport of d9b5b658210f2 ("MIPS: init: Ensure bootmem does not
> corrupt reserved memory").
>
The following change:
8f235d1a3eb71 ('mm: add PHYS_PFN, use it in __phys_to_pfn()')
needs to be backported prior to d9b5b658210f2 to add the missing macro
definition.
thanks,
Marcin
next prev parent reply other threads:[~2017-11-20 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a11b2d4.17f71c0a.5dc3f.fef5@mx.google.com>
[not found] ` <CAK8P3a2QcYoFHFrR+DPFs1Oo6Li1NO=VMxoAyoh=yWF24j4YMg@mail.gmail.com>
2017-11-19 20:55 ` Fwd: stable-rc/linux-4.4.y build: 182 builds: 60 failed, 122 passed, 60 errors, 60 warnings (v4.4.99-60-g803704b287d8) Arnd Bergmann
2017-11-20 9:41 ` Marcin Nowakowski [this message]
2017-11-20 14:51 ` Greg Kroah-Hartman
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=8a278610-716d-321e-a403-6c8e74b05c82@mips.com \
--to=marcin.nowakowski@mips.com \
--cc=alexander.levin@verizon.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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).