From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-acpi@vger.kernel.org, devel@acpica.org,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [pm:bleeding-edge 181/195] kernel/power/snapshot.c:57:3: error: implicit declaration of function 'set_memory_ro'
Date: Sat, 9 Jul 2016 12:24:47 +0800 [thread overview]
Message-ID: <201607091245.53tcFsfP%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head: b2b1e68c40b801c00fa028d7b0b5b542e9740918
commit: 0c96ed43a072c9481f655c3d4fe37f1a90f51c6f [181/195] PM / hibernate: Image data protection during restoration
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 0c96ed43a072c9481f655c3d4fe37f1a90f51c6f
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
kernel/power/snapshot.c: In function 'hibernate_restore_protect_page':
>> kernel/power/snapshot.c:57:3: error: implicit declaration of function 'set_memory_ro' [-Werror=implicit-function-declaration]
set_memory_ro((unsigned long)page_address, 1);
^
kernel/power/snapshot.c: In function 'hibernate_restore_unprotect_page':
>> kernel/power/snapshot.c:63:3: error: implicit declaration of function 'set_memory_rw' [-Werror=implicit-function-declaration]
set_memory_rw((unsigned long)page_address, 1);
^
cc1: some warnings being treated as errors
vim +/set_memory_ro +57 kernel/power/snapshot.c
51 hibernate_restore_protection_active = false;
52 }
53
54 static inline void hibernate_restore_protect_page(void *page_address)
55 {
56 if (hibernate_restore_protection_active)
> 57 set_memory_ro((unsigned long)page_address, 1);
58 }
59
60 static inline void hibernate_restore_unprotect_page(void *page_address)
61 {
62 if (hibernate_restore_protection_active)
> 63 set_memory_rw((unsigned long)page_address, 1);
64 }
65
66 static int swsusp_page_is_free(struct page *);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 46354 bytes --]
reply other threads:[~2016-07-09 4:24 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=201607091245.53tcFsfP%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=devel@acpica.org \
--cc=kbuild-all@01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).