From: kernel test robot <lkp@intel.com>
To: SanjayKumar J <vjsanjay@gmail.com>,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org
Cc: kbuild-all@lists.01.org, SanjayKumar J <vjsanjay@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v2] tools/runqslower: use __state instead of state
Date: Tue, 13 Jul 2021 01:41:35 +0800 [thread overview]
Message-ID: <202107130145.OLy5XU3h-lkp@intel.com> (raw)
In-Reply-To: <20210707051241.20565-1-vjsanjay@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
Hi SanjayKumar,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
[also build test ERROR on vhost/linux-next ipvs/master v5.14-rc1]
[cannot apply to bpf/master next-20210712]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/SanjayKumar-J/tools-runqslower-use-__state-instead-of-state/20210707-131703
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/0e86dc86c0f18512dc19ba3d0b001b3f06338a0d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review SanjayKumar-J/tools-runqslower-use-__state-instead-of-state/20210707-131703
git checkout 0e86dc86c0f18512dc19ba3d0b001b3f06338a0d
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash -C tools/testing/selftests/bpf install
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 >>):
>> runqslower.bpf.c:77:12: error: no member named '__state' in 'struct task_struct'; did you mean 'state'?
if (prev->__state == TASK_RUNNING)
^~~~~~~
state
/tools/vmlinux.h:1096:20: note: 'state' declared here
volatile long int state;
^
1 error generated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41980 bytes --]
next prev parent reply other threads:[~2021-07-12 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 5:12 [PATCH v2] tools/runqslower: use __state instead of state SanjayKumar J
2021-07-12 17:41 ` kernel test robot [this message]
2021-07-14 5:14 ` Sanjay Kumar J
-- strict thread matches above, loose matches on Subject: below --
2021-07-06 18:14 SanjayKumar J
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=202107130145.OLy5XU3h-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kbuild-all@lists.01.org \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=vjsanjay@gmail.com \
--cc=yhs@fb.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).