From: Guenter Roeck <linux@roeck-us.net>
To: Sasha Levin <alexander.levin@verizon.com>,
stable <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: mips/sparc64 build failures in v3.18.38 and v4.1.29
Date: Sun, 31 Jul 2016 17:23:19 -0700 [thread overview]
Message-ID: <579E9677.4090406@roeck-us.net> (raw)
[ again, this time with Sasha's new e-mail address, and updated ]
Build failures in v3.18.38 and 4.1.29:
mips builds:
arch/mips/kernel/setup.c: In function 'arch_mem_init':
arch/mips/kernel/setup.c:689:2: error: implicit declaration of function 'reserve_bootmem_region'
Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for hibernation").
It fixes a bug which does not exist in 3.18 / 4.1, in turn causing all mips builds in 3.18
and 4.1 to fail.
sparc64 builds:
mm/init_64.c: In function 'bootmem_init_numa':
arch/sparc/mm/init_64.c:1311:4: error: 'numa_latency' undeclared
Caused by 0396a871c4e3 ("sparc64: Fix numa node distance initialization").
'numa_latency' does not exist in 3.18 and 4.1. It was introduced upstream with commit
52708d690b8be ("sparc64: Fix numa distance values").
Guenter
reply other threads:[~2016-08-01 0:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=579E9677.4090406@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alexander.levin@verizon.com \
--cc=linux-kernel@vger.kernel.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