linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [pm:bleeding-edge 10/17] kernel/power/snapshot.c:928:5: sparse: symbol 'swsusp_page_is_valid' was not declared. Should it be static?
@ 2015-07-14  8:23 kbuild test robot
  2015-07-14  8:23 ` [PATCH pm] PM / hibernate: swsusp_page_is_valid() can be static kbuild test robot
  0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2015-07-14  8:23 UTC (permalink / raw)
  To: Chen Yu
  Cc: kbuild-all, Rafael J. Wysocki, Lee, Chun-Yi, linux-pm,
	Pavel Machek, Len Brown, linux-kernel

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head:   4835ff4dabfa392ba9f10218231ea8b6972d9459
commit: d09d85e88f60a6e4d9f8159556f024bd588f11f0 [10/17] PM / hibernate: make sure each resuming page is in current memory zones
reproduce:
  # apt-get install sparse
  git checkout d09d85e88f60a6e4d9f8159556f024bd588f11f0
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> kernel/power/snapshot.c:928:5: sparse: symbol 'swsusp_page_is_valid' was not declared. Should it be static?
   kernel/power/snapshot.c:1354:14: sparse: symbol 'alloc_normal' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-07-14 12:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-14  8:23 [pm:bleeding-edge 10/17] kernel/power/snapshot.c:928:5: sparse: symbol 'swsusp_page_is_valid' was not declared. Should it be static? kbuild test robot
2015-07-14  8:23 ` [PATCH pm] PM / hibernate: swsusp_page_is_valid() can be static kbuild test robot
2015-07-14 12:12   ` Chen, Yu C

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).