From: Ingo Molnar <mingo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "kernelci.org bot" <bot@kernelci.org>,
kernel-build-reports@lists.linaro.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
gregkh <gregkh@linuxfoundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-mips@linux-mips.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: next build: 208 builds: 21 failed, 187 passed, 53 errors, 406 warnings (next-20170308)
Date: Wed, 8 Mar 2017 10:42:03 +0100 [thread overview]
Message-ID: <20170308094203.GA1523@gmail.com> (raw)
In-Reply-To: <CAK8P3a16cpvK3_a0Rxx+XqRw_d97LtVgpzcpvpzmH6U4Ty-fXQ@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> wrote:
> > bmips_be_defconfig (mips) — FAIL, 1 error, 1 warning, 0 section mismatches
> >
> > Errors:
> > arch/mips/kernel/smp-bmips.c:183:38: error: implicit declaration of function
> > 'task_stack_page' [-Werror=implicit-function-declaration]
>
> A new regression from the end of the merge window, also present in mainline.
> I sent a fix yesterday, addressing various mips build failures.
Haven't heard from Ralf yet, so I've applied your patch to tip:core/urgent and
will get it to Linus ASAP (i.e. later today), to minimize the size of the
build-breakage window.
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: next build: 208 builds: 21 failed, 187 passed, 53 errors, 406 warnings (next-20170308)
Date: Wed, 8 Mar 2017 10:42:03 +0100 [thread overview]
Message-ID: <20170308094203.GA1523@gmail.com> (raw)
In-Reply-To: <CAK8P3a16cpvK3_a0Rxx+XqRw_d97LtVgpzcpvpzmH6U4Ty-fXQ@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> wrote:
> > bmips_be_defconfig (mips) ? FAIL, 1 error, 1 warning, 0 section mismatches
> >
> > Errors:
> > arch/mips/kernel/smp-bmips.c:183:38: error: implicit declaration of function
> > 'task_stack_page' [-Werror=implicit-function-declaration]
>
> A new regression from the end of the merge window, also present in mainline.
> I sent a fix yesterday, addressing various mips build failures.
Haven't heard from Ralf yet, so I've applied your patch to tip:core/urgent and
will get it to Linus ASAP (i.e. later today), to minimize the size of the
build-breakage window.
Thanks,
Ingo
next prev parent reply other threads:[~2017-03-08 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58bf7d43.8173190a.8d21e.1fde@mx.google.com>
2017-03-08 8:24 ` next build: 208 builds: 21 failed, 187 passed, 53 errors, 406 warnings (next-20170308) Arnd Bergmann
2017-03-08 8:24 ` Arnd Bergmann
2017-03-08 8:42 ` gregkh
2017-03-08 8:42 ` gregkh
2017-03-08 9:42 ` Ingo Molnar [this message]
2017-03-08 9:42 ` Ingo Molnar
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=20170308094203.GA1523@gmail.com \
--to=mingo@kernel.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@redhat.com \
/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.