All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sanjay Kumar J <vjsanjay@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>, Martin Lau <kafai@fb.com>,
	Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
	john fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	kbuild-all@lists.01.org, Networking <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] tools/runqslower: use __state instead of state
Date: Wed, 14 Jul 2021 10:44:08 +0530	[thread overview]
Message-ID: <CAN7cG1a1sSQLuotMie44-SHyCQu5E1QCWwJxhqvVWGASaLh1PA@mail.gmail.com> (raw)
In-Reply-To: <202107130145.OLy5XU3h-lkp@intel.com>

On Mon, Jul 12, 2021 at 11:12 PM kernel test robot <lkp@intel.com> wrote:
>
> 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.
v4 version of the patch is already accepted in bpf tree
commit-id:5616e895ecc56 and also in net tree ommit:5616e895ecc56
> 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

WARNING: multiple messages have this Message-ID (diff)
From: Sanjay Kumar J <vjsanjay@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2] tools/runqslower: use __state instead of state
Date: Wed, 14 Jul 2021 10:44:08 +0530	[thread overview]
Message-ID: <CAN7cG1a1sSQLuotMie44-SHyCQu5E1QCWwJxhqvVWGASaLh1PA@mail.gmail.com> (raw)
In-Reply-To: <202107130145.OLy5XU3h-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]

On Mon, Jul 12, 2021 at 11:12 PM kernel test robot <lkp@intel.com> wrote:
>
> 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.
v4 version of the patch is already accepted in bpf tree
commit-id:5616e895ecc56 and also in net tree ommit:5616e895ecc56
> 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(a)lists.01.org

  reply	other threads:[~2021-07-14  5:13 UTC|newest]

Thread overview: 6+ 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
2021-07-12 17:41   ` kernel test robot
2021-07-14  5:14   ` Sanjay Kumar J [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=CAN7cG1a1sSQLuotMie44-SHyCQu5E1QCWwJxhqvVWGASaLh1PA@mail.gmail.com \
    --to=vjsanjay@gmail.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=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.