LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [clk:test-sched-packing-tasks-freq 10820/10847] kernel/sched/fair.c:199:1: sparse: symbol '__pcpu_scope_sd_pack_buddy' was not declared. Should it be static?
Date: Sat, 24 Jan 2015 10:44:57 +0800	[thread overview]
Message-ID: <201501241041.Cc4XnwuN%fengguang.wu@intel.com> (raw)

tree:   https://git.linaro.org/people/mturquette/linux.git test-sched-packing-tasks-freq
head:   3add111981928a9ce810cd1b1956dc39e6c2445f
commit: 9cb183281a03911e724a648832d9f096c09197fe [10820/10847] sched: packing tasks
reproduce:
  # apt-get install sparse
  git checkout 9cb183281a03911e724a648832d9f096c09197fe
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   kernel/sched/fair.c:51:14: sparse: symbol 'normalized_sysctl_sched_latency' was not declared. Should it be static?
   kernel/sched/fair.c:70:14: sparse: symbol 'normalized_sysctl_sched_min_granularity' was not declared. Should it be static?
   kernel/sched/fair.c:92:14: sparse: symbol 'normalized_sysctl_sched_wakeup_granularity' was not declared. Should it be static?
>> kernel/sched/fair.c:199:1: sparse: symbol '__pcpu_scope_sd_pack_buddy' was not declared. Should it be static?
   kernel/sched/sched.h:765:9: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:249:22: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:4993:14: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:1666:14: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:2168:15: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7571:22: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7586:9: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:5070:9: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:5126:17: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:5706:41: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:5742:41: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7688:9: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7755:17: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7839:14: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7727:16: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7921:9: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7727:16: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:7822:14: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:8091:14: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:8103:14: sparse: incompatible types in comparison expression (different address spaces)
   kernel/sched/fair.c:8112:14: sparse: incompatible types in comparison expression (different address spaces)

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

             reply	other threads:[~2015-01-24  2:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24  2:44 kbuild test robot [this message]
2015-01-24  2:44 ` [PATCH clk] sched: __pcpu_scope_sd_pack_buddy can be static kbuild test robot

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=201501241041.Cc4XnwuN%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.org \
    --subject='Re: [clk:test-sched-packing-tasks-freq 10820/10847] kernel/sched/fair.c:199:1: sparse: symbol '\''__pcpu_scope_sd_pack_buddy'\'' was not declared. Should it be static?' \
    /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

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