From: kernel test robot <lkp@intel.com>
To: Tomer Maimon <tmaimon77@gmail.com>,
mturquette@baylibre.com, sboyd@kernel.org,
p.zabel@pengutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, tali.perry1@gmail.com,
joel@jms.id.au, venture@google.com, yuenn@google.com,
benjaminfair@google.com
Cc: oe-kbuild-all@lists.linux.dev, devicetree@vger.kernel.org,
openbmc@lists.ozlabs.org, Tomer Maimon <tmaimon77@gmail.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v24 2/4] reset: npcm: register npcm8xx clock auxiliary bus device
Date: Fri, 10 May 2024 19:25:56 +0800 [thread overview]
Message-ID: <202405101846.avdHTXi3-lkp@intel.com> (raw)
In-Reply-To: <20240509192411.2432066-3-tmaimon77@gmail.com>
Hi Tomer,
kernel test robot noticed the following build warnings:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on pza/reset/next linus/master v6.9-rc7 next-20240510]
[cannot apply to pza/imx-drm/next]
[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/Tomer-Maimon/dt-bindings-reset-npcm-add-clock-properties/20240510-072622
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
patch link: https://lore.kernel.org/r/20240509192411.2432066-3-tmaimon77%40gmail.com
patch subject: [PATCH v24 2/4] reset: npcm: register npcm8xx clock auxiliary bus device
config: i386-buildonly-randconfig-002-20240510 (https://download.01.org/0day-ci/archive/20240510/202405101846.avdHTXi3-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240510/202405101846.avdHTXi3-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/202405101846.avdHTXi3-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/reset/reset-npcm.c: In function 'npcm_clock_adev_release':
drivers/reset/reset-npcm.c:391:2: error: implicit declaration of function 'kfree'; did you mean 'vfree'? [-Werror=implicit-function-declaration]
kfree(rdev);
^~~~~
vfree
drivers/reset/reset-npcm.c: In function 'npcm_clock_adev_alloc':
drivers/reset/reset-npcm.c:400:9: error: implicit declaration of function 'kzalloc'; did you mean 'vzalloc'? [-Werror=implicit-function-declaration]
rdev = kzalloc(sizeof(*rdev), GFP_KERNEL);
^~~~~~~
vzalloc
>> drivers/reset/reset-npcm.c:400:7: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
rdev = kzalloc(sizeof(*rdev), GFP_KERNEL);
^
cc1: some warnings being treated as errors
vim +400 drivers/reset/reset-npcm.c
385
386 static void npcm_clock_adev_release(struct device *dev)
387 {
388 struct auxiliary_device *adev = to_auxiliary_dev(dev);
389 struct npcm_clock_adev *rdev = to_npcm_clock_adev(adev);
390
> 391 kfree(rdev);
392 }
393
394 static struct auxiliary_device *npcm_clock_adev_alloc(struct npcm_rc_data *rst_data, char *clk_name)
395 {
396 struct npcm_clock_adev *rdev;
397 struct auxiliary_device *adev;
398 int ret;
399
> 400 rdev = kzalloc(sizeof(*rdev), GFP_KERNEL);
401 if (!rdev)
402 return ERR_PTR(-ENOMEM);
403
404 rdev->base = rst_data->base;
405
406 adev = &rdev->adev;
407 adev->name = clk_name;
408 adev->dev.parent = rst_data->dev;
409 adev->dev.release = npcm_clock_adev_release;
410 adev->id = 555u;
411
412 ret = auxiliary_device_init(adev);
413 if (ret) {
414 kfree(adev);
415 return ERR_PTR(ret);
416 }
417
418 return adev;
419 }
420
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Tomer Maimon <tmaimon77@gmail.com>,
mturquette@baylibre.com, sboyd@kernel.org,
p.zabel@pengutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, tali.perry1@gmail.com,
joel@jms.id.au, venture@google.com, yuenn@google.com,
benjaminfair@google.com
Cc: devicetree@vger.kernel.org, Tomer Maimon <tmaimon77@gmail.com>,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev, linux-clk@vger.kernel.org
Subject: Re: [PATCH v24 2/4] reset: npcm: register npcm8xx clock auxiliary bus device
Date: Fri, 10 May 2024 19:25:56 +0800 [thread overview]
Message-ID: <202405101846.avdHTXi3-lkp@intel.com> (raw)
In-Reply-To: <20240509192411.2432066-3-tmaimon77@gmail.com>
Hi Tomer,
kernel test robot noticed the following build warnings:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on pza/reset/next linus/master v6.9-rc7 next-20240510]
[cannot apply to pza/imx-drm/next]
[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/Tomer-Maimon/dt-bindings-reset-npcm-add-clock-properties/20240510-072622
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
patch link: https://lore.kernel.org/r/20240509192411.2432066-3-tmaimon77%40gmail.com
patch subject: [PATCH v24 2/4] reset: npcm: register npcm8xx clock auxiliary bus device
config: i386-buildonly-randconfig-002-20240510 (https://download.01.org/0day-ci/archive/20240510/202405101846.avdHTXi3-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240510/202405101846.avdHTXi3-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/202405101846.avdHTXi3-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/reset/reset-npcm.c: In function 'npcm_clock_adev_release':
drivers/reset/reset-npcm.c:391:2: error: implicit declaration of function 'kfree'; did you mean 'vfree'? [-Werror=implicit-function-declaration]
kfree(rdev);
^~~~~
vfree
drivers/reset/reset-npcm.c: In function 'npcm_clock_adev_alloc':
drivers/reset/reset-npcm.c:400:9: error: implicit declaration of function 'kzalloc'; did you mean 'vzalloc'? [-Werror=implicit-function-declaration]
rdev = kzalloc(sizeof(*rdev), GFP_KERNEL);
^~~~~~~
vzalloc
>> drivers/reset/reset-npcm.c:400:7: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
rdev = kzalloc(sizeof(*rdev), GFP_KERNEL);
^
cc1: some warnings being treated as errors
vim +400 drivers/reset/reset-npcm.c
385
386 static void npcm_clock_adev_release(struct device *dev)
387 {
388 struct auxiliary_device *adev = to_auxiliary_dev(dev);
389 struct npcm_clock_adev *rdev = to_npcm_clock_adev(adev);
390
> 391 kfree(rdev);
392 }
393
394 static struct auxiliary_device *npcm_clock_adev_alloc(struct npcm_rc_data *rst_data, char *clk_name)
395 {
396 struct npcm_clock_adev *rdev;
397 struct auxiliary_device *adev;
398 int ret;
399
> 400 rdev = kzalloc(sizeof(*rdev), GFP_KERNEL);
401 if (!rdev)
402 return ERR_PTR(-ENOMEM);
403
404 rdev->base = rst_data->base;
405
406 adev = &rdev->adev;
407 adev->name = clk_name;
408 adev->dev.parent = rst_data->dev;
409 adev->dev.release = npcm_clock_adev_release;
410 adev->id = 555u;
411
412 ret = auxiliary_device_init(adev);
413 if (ret) {
414 kfree(adev);
415 return ERR_PTR(ret);
416 }
417
418 return adev;
419 }
420
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-10 11:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 19:24 [PATCH v24 0/4] Introduce Nuvoton Arbel NPCM8XX BMC SoC Tomer Maimon
2024-05-09 19:24 ` Tomer Maimon
2024-05-09 19:24 ` [PATCH v24 1/4] dt-bindings: reset: npcm: add clock properties Tomer Maimon
2024-05-09 19:24 ` Tomer Maimon
2024-05-13 15:51 ` Rob Herring
2024-05-13 15:51 ` Rob Herring
2024-05-16 9:47 ` Tomer Maimon
2024-05-16 9:47 ` Tomer Maimon
2024-05-09 19:24 ` [PATCH v24 2/4] reset: npcm: register npcm8xx clock auxiliary bus device Tomer Maimon
2024-05-09 19:24 ` Tomer Maimon
2024-05-10 10:33 ` kernel test robot
2024-05-10 10:33 ` kernel test robot
2024-05-10 11:25 ` kernel test robot [this message]
2024-05-10 11:25 ` kernel test robot
2024-05-10 11:25 ` kernel test robot
2024-05-10 11:25 ` kernel test robot
2024-05-09 19:24 ` [PATCH v24 3/4] clk: npcm8xx: add clock controller Tomer Maimon
2024-05-09 19:24 ` Tomer Maimon
2024-05-09 19:24 ` [PATCH v24 4/4] dt-binding: clock: remove nuvoton npcm845-clk bindings Tomer Maimon
2024-05-09 19:24 ` Tomer Maimon
2024-05-13 15:53 ` Rob Herring
2024-05-13 15:53 ` Rob Herring
2024-05-16 9:44 ` Tomer Maimon
2024-05-16 9:44 ` Tomer Maimon
2024-05-22 16:34 ` Tomer Maimon
2024-05-22 16:34 ` Tomer Maimon
2024-05-25 18:58 ` Krzysztof Kozlowski
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=202405101846.avdHTXi3-lkp@intel.com \
--to=lkp@intel.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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.