From: kernel test robot <lkp@intel.com>
To: Stephen Dickey <quic_dickey@quicinc.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@gnuweeb.org>,
linux-kernel@vger.kernel.org, Todd Kjos <tkjos@google.com>
Subject: [ammarfaizi2-block:google/android/kernel/common/android13-5.15 2898/2936] kernel/sched/sched.h:1553:15: error: must use 'struct' tag to refer to type 'rq'
Date: Tue, 25 Jan 2022 08:26:36 +0800 [thread overview]
Message-ID: <202201250831.PBiV30bo-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android13-5.15
head: b7e4947b29bb8d0351c581d9365780d9b6f4d702
commit: 50f5345c8756129044a3246800f51f04ae2f55b0 [2898/2936] ANDROID: __migrate_task header
config: arm-randconfig-r003-20220124 (https://download.01.org/0day-ci/archive/20220125/202201250831.PBiV30bo-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 2e58a18910867ba6795066e044293e6daf89edf5)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://github.com/ammarfaizi2/linux-block/commit/50f5345c8756129044a3246800f51f04ae2f55b0
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android13-5.15
git checkout 50f5345c8756129044a3246800f51f04ae2f55b0
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash kernel/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from kernel/sched/core.c:13:
>> kernel/sched/sched.h:1553:15: error: must use 'struct' tag to refer to type 'rq'
static inline rq *__migrate_task(struct rq *rq, struct rq_flags *rf,
^
struct
1 error generated.
--
In file included from kernel/sched/fair.c:23:
>> kernel/sched/sched.h:1553:15: error: must use 'struct' tag to refer to type 'rq'
static inline rq *__migrate_task(struct rq *rq, struct rq_flags *rf,
^
struct
kernel/sched/fair.c:628:5: warning: no previous prototype for function 'sched_update_scaling' [-Wmissing-prototypes]
int sched_update_scaling(void)
^
kernel/sched/fair.c:628:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int sched_update_scaling(void)
^
static
kernel/sched/fair.c:4494:6: warning: no previous prototype for function 'set_next_entity' [-Wmissing-prototypes]
void set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
^
kernel/sched/fair.c:4494:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
^
static
2 warnings and 1 error generated.
--
In file included from kernel/sched/rt.c:6:
>> kernel/sched/sched.h:1553:15: error: must use 'struct' tag to refer to type 'rq'
static inline rq *__migrate_task(struct rq *rq, struct rq_flags *rf,
^
struct
kernel/sched/rt.c:677:6: warning: no previous prototype for function 'sched_rt_bandwidth_account' [-Wmissing-prototypes]
bool sched_rt_bandwidth_account(struct rt_rq *rt_rq)
^
kernel/sched/rt.c:677:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
bool sched_rt_bandwidth_account(struct rt_rq *rt_rq)
^
static
1 warning and 1 error generated.
vim +1553 kernel/sched/sched.h
1548
1549 #ifdef CONFIG_SMP
1550 extern struct rq *__migrate_task(struct rq *rq, struct rq_flags *rf,
1551 struct task_struct *p, int dest_cpu);
1552 #else /* !CONFIG_SMP */
> 1553 static inline rq *__migrate_task(struct rq *rq, struct rq_flags *rf,
1554 struct task_struct *p, int dest_cpu) { return rq; }
1555 #endif
1556
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-25 0:27 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=202201250831.PBiV30bo-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwml@gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=quic_dickey@quicinc.com \
--cc=tkjos@google.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;
as well as URLs for NNTP newsgroup(s).