From: kbuild test robot <fengguang.wu@intel.com>
To: Rik van Riel <riel@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: [tip:sched/core 93/94] kernel/sched/fair.c:2656:44: warning: 'struct sched_domain' declared inside parameter list will not be visible outside of this definition or declaration
Date: Sat, 24 Jun 2017 17:24:33 +0800 [thread overview]
Message-ID: <201706241730.RgOjfIij%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head: 815abf5af45f04f759f12f3172afd15226fd7f71
commit: 3fed382b46baac83703130fe4cd3d9147f427fb9 [93/94] sched/numa: Implement NUMA node level wake_affine()
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 3fed382b46baac83703130fe4cd3d9147f427fb9
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> kernel/sched/fair.c:2656:44: warning: 'struct sched_domain' declared inside parameter list will not be visible outside of this definition or declaration
static inline bool numa_wake_affine(struct sched_domain *sd,
^~~~~~~~~~~~
vim +2656 kernel/sched/fair.c
2640
2641 return true;
2642 }
2643 #else
2644 static void task_tick_numa(struct rq *rq, struct task_struct *curr)
2645 {
2646 }
2647
2648 static inline void account_numa_enqueue(struct rq *rq, struct task_struct *p)
2649 {
2650 }
2651
2652 static inline void account_numa_dequeue(struct rq *rq, struct task_struct *p)
2653 {
2654 }
2655
> 2656 static inline bool numa_wake_affine(struct sched_domain *sd,
2657 struct task_struct *p, int this_cpu,
2658 int prev_cpu, int sync)
2659 {
2660 return true;
2661 }
2662 #endif /* CONFIG_NUMA_BALANCING */
2663
2664 static void
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6567 bytes --]
reply other threads:[~2017-06-24 9: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=201706241730.RgOjfIij%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=tipbuild@zytor.com \
/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
all inboxes | Powered by JetHome®