From: kernel test robot <lkp@intel.com>
To: Wang Ming <machel@vivo.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] reset: hisilicon: Use dev_err_probe instead of dev_err
Date: Wed, 19 Jul 2023 08:48:57 +0800 [thread overview]
Message-ID: <202307190847.UjE7NAlJ-lkp@intel.com> (raw)
In-Reply-To: <20230718030511.16065-1-machel@vivo.com>
Hi Wang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pza/reset/next]
[also build test WARNING on pza/imx-drm/next linus/master v6.5-rc2 next-20230718]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Wang-Ming/reset-hisilicon-Use-dev_err_probe-instead-of-dev_err/20230718-203055
base: https://git.pengutronix.de/git/pza/linux reset/next
patch link: https://lore.kernel.org/r/20230718030511.16065-1-machel%40vivo.com
patch subject: [PATCH v1] reset: hisilicon: Use dev_err_probe instead of dev_err
config: arm-defconfig (https://download.01.org/0day-ci/archive/20230719/202307190847.UjE7NAlJ-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230719/202307190847.UjE7NAlJ-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/202307190847.UjE7NAlJ-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/reset/hisilicon/reset-hi3660.c: In function 'hi3660_reset_probe':
>> drivers/reset/hisilicon/reset-hi3660.c:93:36: warning: passing argument 2 of 'dev_err_probe' makes integer from pointer without a cast [-Wint-conversion]
93 | dev_err_probe(dev, "failed to get hisilicon,rst-syscon\n");
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| char *
In file included from include/linux/platform_device.h:13,
from include/linux/of_device.h:5,
from drivers/reset/hisilicon/reset-hi3660.c:9:
include/linux/device.h:1091:64: note: expected 'int' but argument is of type 'char *'
1091 | __printf(3, 4) int dev_err_probe(const struct device *dev, int err, const char *fmt, ...);
| ~~~~^~~
drivers/reset/hisilicon/reset-hi3660.c:93:17: error: too few arguments to function 'dev_err_probe'
93 | dev_err_probe(dev, "failed to get hisilicon,rst-syscon\n");
| ^~~~~~~~~~~~~
include/linux/device.h:1091:20: note: declared here
1091 | __printf(3, 4) int dev_err_probe(const struct device *dev, int err, const char *fmt, ...);
| ^~~~~~~~~~~~~
vim +/dev_err_probe +93 drivers/reset/hisilicon/reset-hi3660.c
75
76 static int hi3660_reset_probe(struct platform_device *pdev)
77 {
78 struct hi3660_reset_controller *rc;
79 struct device_node *np = pdev->dev.of_node;
80 struct device *dev = &pdev->dev;
81
82 rc = devm_kzalloc(dev, sizeof(*rc), GFP_KERNEL);
83 if (!rc)
84 return -ENOMEM;
85
86 rc->map = syscon_regmap_lookup_by_phandle(np, "hisilicon,rst-syscon");
87 if (rc->map == ERR_PTR(-ENODEV)) {
88 /* fall back to the deprecated compatible */
89 rc->map = syscon_regmap_lookup_by_phandle(np,
90 "hisi,rst-syscon");
91 }
92 if (IS_ERR(rc->map)) {
> 93 dev_err_probe(dev, "failed to get hisilicon,rst-syscon\n");
94 return PTR_ERR(rc->map);
95 }
96
97 rc->rst.ops = &hi3660_reset_ops,
98 rc->rst.of_node = np;
99 rc->rst.of_reset_n_cells = 2;
100 rc->rst.of_xlate = hi3660_reset_xlate;
101
102 return reset_controller_register(&rc->rst);
103 }
104
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-19 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 3:04 [PATCH v1] reset: hisilicon: Use dev_err_probe instead of dev_err Wang Ming
2023-07-19 0:48 ` kernel test robot [this message]
2023-07-19 2:57 ` kernel test robot
2023-07-19 3:02 ` 回复: " 王明-软件底层技术部
2023-07-19 5:04 ` 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=202307190847.UjE7NAlJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=machel@vivo.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=opensource.kernel@vivo.com \
--cc=p.zabel@pengutronix.de \
/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