From: 陈华才 <chenhc@lemote.com>
To: "Guenter Roeck" <linux@roeck-us.net>,
"Sasha Levin" <sasha.levin@oracle.com>,
"alexander.levin" <alexander.levin@verizon.com>
Cc: stable <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re:mips builds failing in v3.18.38 and v4.1.29
Date: Mon, 1 Aug 2016 09:56:28 +0800 [thread overview]
Message-ID: <tencent_68698C88769DDED5414E72F2@qq.com> (raw)
In-Reply-To: <579E905E.3000706@roeck-us.net>
Hi,
I have already told Sasha that "MIPS: Reserve nosave data for hibernation" should not be backported to 4.1/3.18. But he has no response.
Huacai
------------------ Original ------------------
From: "Guenter Roeck"<linux@roeck-us.net>;
Date: Mon, Aug 1, 2016 07:57 AM
To: "Sasha Levin"<sasha.levin@oracle.com>;
Cc: "stable"<stable@vger.kernel.org>; "linux-kernel@vger.kernel.org"<linux-kernel@vger.kernel.org>; "Huacai Chen"<chenhc@lemote.com>;
Subject: mips builds failing in v3.18.38 and v4.1.29
Sorry I didn't notice earlier - my 3.18/4.1 build scripts were broken.
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.
Guenter
next prev parent reply other threads:[~2016-08-01 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 23:57 mips builds failing in v3.18.38 and v4.1.29 Guenter Roeck
2016-08-01 1:56 ` 陈华才 [this message]
2016-08-01 14:58 ` Levin, Alexander
2016-08-01 15:29 ` mips " Guenter Roeck
2016-08-01 15:37 ` Levin, Alexander
2016-08-01 21:23 ` Guenter Roeck
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=tencent_68698C88769DDED5414E72F2@qq.com \
--to=chenhc@lemote.com \
--cc=alexander.levin@verizon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=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