From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [cel:kdevops 58/58] net/sunrpc/clnt.c:2341:9: error: no member named 'tk_pid' in 'struct rpc_task'
Date: Wed, 3 Jan 2024 20:40:00 +0800 [thread overview]
Message-ID: <202401032013.Qirj77i8-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux kdevops
head: 8bcbb6048716f07d335466d70ae8659d998d43c7
commit: 8bcbb6048716f07d335466d70ae8659d998d43c7 [58/58] Debugging
config: riscv-rv32_defconfig (https://download.01.org/0day-ci/archive/20240103/202401032013.Qirj77i8-lkp@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project baf8a39aaf8b61a38b5b2b5591deb765e42eb00b)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240103/202401032013.Qirj77i8-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202401032013.Qirj77i8-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/sunrpc/clnt.c:2341:9: error: no member named 'tk_pid' in 'struct rpc_task'
2341 | task->tk_pid,
| ~~~~ ^
net/sunrpc/clnt.c:2357:9: error: no member named 'tk_pid' in 'struct rpc_task'
2357 | task->tk_pid,
| ~~~~ ^
net/sunrpc/clnt.c:2380:9: error: no member named 'tk_pid' in 'struct rpc_task'
2380 | task->tk_pid,
| ~~~~ ^
3 errors generated.
vim +2341 net/sunrpc/clnt.c
2336
2337 static void
2338 call_bc_encode(struct rpc_task *task)
2339 {
2340 trace_printk("%08x@%08x tk_status=%d",
> 2341 task->tk_pid,
2342 task->tk_client ? task->tk_client->cl_clid : -1,
2343 task->tk_status);
2344
2345 xprt_request_enqueue_transmit(task);
2346 task->tk_action = call_bc_transmit;
2347 }
2348
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-03 12:41 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=202401032013.Qirj77i8-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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