From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: sparse: incorrect type in return expression (different base types)
Date: Wed, 05 Jan 2022 19:33:25 +0800 [thread overview]
Message-ID: <202201051942.CihtR2Ia-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2613 bytes --]
tree: https://github.com/0day-ci/linux/commits/UPDATE-20220105-144328/Miaoqian-Lin/remoteproc-Fix-NULL-vs-IS_ERR-checking-in-rproc_create_trace_file/20211227-170725
head: e2c26738760efa9568ce3fef6180fb4311e28d08
commit: e2c26738760efa9568ce3fef6180fb4311e28d08 remoteproc: Fix NULL vs IS_ERR() checking in rproc_create_trace_file
date: 5 hours ago
config: powerpc-randconfig-s031-20220105 (https://download.01.org/0day-ci/archive/20220105/202201051942.CihtR2Ia-lkp(a)intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/e2c26738760efa9568ce3fef6180fb4311e28d08
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review UPDATE-20220105-144328/Miaoqian-Lin/remoteproc-Fix-NULL-vs-IS_ERR-checking-in-rproc_create_trace_file/20211227-170725
git checkout e2c26738760efa9568ce3fef6180fb4311e28d08
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=powerpc SHELL=/bin/bash drivers/input/touchscreen/ drivers/remoteproc/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: sparse: incorrect type in return expression (different base types) @@ expected struct dentry * @@ got long @@
drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: expected struct dentry *
drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: got long
vim +395 drivers/remoteproc/remoteproc_debugfs.c
385
386 struct dentry *rproc_create_trace_file(const char *name, struct rproc *rproc,
387 struct rproc_debug_trace *trace)
388 {
389 struct dentry *tfile;
390
391 tfile = debugfs_create_file(name, 0400, rproc->dbg_dir, trace,
392 &trace_rproc_ops);
393 if (IS_ERR(tfile)) {
394 dev_err(&rproc->dev, "failed to create debugfs trace entry\n");
> 395 return PTR_ERR(tfile);
396 }
397
398 return tfile;
399 }
400
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
0day robot <lkp@intel.com>
Subject: drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: sparse: incorrect type in return expression (different base types)
Date: Wed, 5 Jan 2022 19:33:25 +0800 [thread overview]
Message-ID: <202201051942.CihtR2Ia-lkp@intel.com> (raw)
tree: https://github.com/0day-ci/linux/commits/UPDATE-20220105-144328/Miaoqian-Lin/remoteproc-Fix-NULL-vs-IS_ERR-checking-in-rproc_create_trace_file/20211227-170725
head: e2c26738760efa9568ce3fef6180fb4311e28d08
commit: e2c26738760efa9568ce3fef6180fb4311e28d08 remoteproc: Fix NULL vs IS_ERR() checking in rproc_create_trace_file
date: 5 hours ago
config: powerpc-randconfig-s031-20220105 (https://download.01.org/0day-ci/archive/20220105/202201051942.CihtR2Ia-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/e2c26738760efa9568ce3fef6180fb4311e28d08
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review UPDATE-20220105-144328/Miaoqian-Lin/remoteproc-Fix-NULL-vs-IS_ERR-checking-in-rproc_create_trace_file/20211227-170725
git checkout e2c26738760efa9568ce3fef6180fb4311e28d08
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=powerpc SHELL=/bin/bash drivers/input/touchscreen/ drivers/remoteproc/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: sparse: incorrect type in return expression (different base types) @@ expected struct dentry * @@ got long @@
drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: expected struct dentry *
drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: got long
vim +395 drivers/remoteproc/remoteproc_debugfs.c
385
386 struct dentry *rproc_create_trace_file(const char *name, struct rproc *rproc,
387 struct rproc_debug_trace *trace)
388 {
389 struct dentry *tfile;
390
391 tfile = debugfs_create_file(name, 0400, rproc->dbg_dir, trace,
392 &trace_rproc_ops);
393 if (IS_ERR(tfile)) {
394 dev_err(&rproc->dev, "failed to create debugfs trace entry\n");
> 395 return PTR_ERR(tfile);
396 }
397
398 return tfile;
399 }
400
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-01-05 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 11:33 kernel test robot [this message]
2022-01-05 11:33 ` drivers/remoteproc/remoteproc_debugfs.c:395:31: sparse: sparse: incorrect type in return expression (different base types) kernel test robot
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=202201051942.CihtR2Ia-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.