From: Guenter Roeck <linux@roeck-us.net>
To: stable <stable@vger.kernel.org>, Sasha Levin <sasha.levin@oracle.com>
Subject: Build error in 3.18.y-stable-queue (s390)
Date: Tue, 22 Mar 2016 20:42:53 -0700 [thread overview]
Message-ID: <56F210BD.1060301@roeck-us.net> (raw)
Hi Sasha,
s390 builds in v3.18.y-stable-queue fail as follows.
./arch/s390/include/asm/mmu_context.h: In function 'init_new_context':
./arch/s390/include/asm/mmu_context.h:33:3: error: implicit declaration of function 'mm_inc_nr_pmds'
Culprit appears to be 's390/mm: four page table levels vs. fork'. It uses mm_inc_nr_pmds(),
which does not exist in v3.18.
I noticed that arm64:allmodconfig builds fail as well, but that is not a new problem and
only seen with gcc 5.2 (or at least not with gcc 4.9.1). I'll see if I can track this down.
Guenter
next reply other threads:[~2016-03-23 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 3:42 Guenter Roeck [this message]
2016-03-23 4:21 ` Build error in 3.18.y-stable-queue (s390) Guenter Roeck
2016-03-24 12:38 ` Sasha Levin
2016-03-24 18:01 ` Guenter Roeck
2016-03-27 5:41 ` Sasha Levin
2016-03-27 15:35 ` Guenter Roeck
2016-03-28 17:07 ` Sasha Levin
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=56F210BD.1060301@roeck-us.net \
--to=linux@roeck-us.net \
--cc=sasha.levin@oracle.com \
--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).