From: Guenter Roeck <linux@roeck-us.net>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org
Subject: build failure in v3.12-stable-queue
Date: Fri, 28 Apr 2017 11:06:47 -0700 [thread overview]
Message-ID: <20170428180647.GA4277@roeck-us.net> (raw)
Hi Jiri,
I see the following build failure in v3.12-stable-queue.
Building mips:cavium_octeon_defconfig ... failed
--------------
Error log:
arch/mips/mm/tlbex.c: In function 'build_huge_handler_tail':
arch/mips/mm/tlbex.c:782:6: error: 'cpu_has_ftlb' undeclared (first use in this function)
if (cpu_has_ftlb && flush) {
^
arch/mips/mm/tlbex.c:782:6: note: each undeclared identifier is reported only once for each function it appears in
In file included from include/linux/bug.h:4:0,
from arch/mips/mm/tlbex.c:24:
arch/mips/mm/tlbex.c:783:11: error: 'cpu_has_tlbinv' undeclared (first use in this function)
BUG_ON(!cpu_has_tlbinv);
^
arch/mips/include/asm/bug.h:33:44: note: in definition of macro 'BUG_ON'
#define BUG_ON(C) __BUG_ON((unsigned long)(C))
^
arch/mips/mm/tlbex.c:786:27: error: 'MIPS_ENTRYHI_EHINV' undeclared (first use in this function)
uasm_i_ori(p, ptr, ptr, MIPS_ENTRYHI_EHINV);
Let me know if I need to bisect.
Thanks,
Guenter
next reply other threads:[~2017-04-28 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 18:06 Guenter Roeck [this message]
2017-04-28 19:04 ` build failure in v3.12-stable-queue Jiri Slaby
2017-04-28 21:06 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2016-07-12 13:30 Build " Guenter Roeck
2016-07-12 13:51 ` Jiri Slaby
2016-07-12 21:23 ` Guenter Roeck
2016-07-13 5:12 ` Michal Kubecek
2016-07-13 9:18 ` Jiri Slaby
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=20170428180647.GA4277@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jslaby@suse.cz \
--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.