From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] clk: rework clk_register to use the clk_hw API
Date: Wed, 20 May 2020 08:24:35 +0800 [thread overview]
Message-ID: <202005200802.CbKffDga%lkp@intel.com> (raw)
In-Reply-To: <20200519170733.295100-1-jbrunet@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 3299 bytes --]
Hi Jerome,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on clk/clk-next]
[also build test ERROR on v5.7-rc6 next-20200519]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Jerome-Brunet/clk-rework-clk_register-to-use-the-clk_hw-API/20200520-011000
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: arm-randconfig-r033-20200519 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 135b877874fae96b4372c8a3fbfaa8ff44ff86e3)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/clk/clk.c:3868:8: error: implicit declaration of function 'clk_hw_get_clk' [-Werror,-Wimplicit-function-declaration]
clk = clk_hw_get_clk(hw);
^
drivers/clk/clk.c:3868:8: note: did you mean '__clk_hw_set_clk'?
include/linux/clk-provider.h:1121:20: note: '__clk_hw_set_clk' declared here
static inline void __clk_hw_set_clk(struct clk_hw *dst, struct clk_hw *src)
^
>> drivers/clk/clk.c:3868:6: warning: incompatible integer to pointer conversion assigning to 'struct clk *' from 'int' [-Wint-conversion]
clk = clk_hw_get_clk(hw);
^ ~~~~~~~~~~~~~~~~~~
1 warning and 1 error generated.
vim +/clk_hw_get_clk +3868 drivers/clk/clk.c
3846
3847 /**
3848 * clk_register - allocate a new clock, register it and return an opaque cookie
3849 * @dev: device that is registering this clock
3850 * @hw: link to hardware-specific clock data
3851 *
3852 * clk_register is the *deprecated* interface for populating the clock tree with
3853 * new clock nodes. Use clk_hw_register() instead.
3854 *
3855 * Returns: a pointer to the newly allocated struct clk which
3856 * cannot be dereferenced by driver code but may be used in conjunction with the
3857 * rest of the clock API. In the event of an error clk_register will return an
3858 * error code; drivers must test for an error code after calling clk_register.
3859 */
3860 struct clk *clk_register(struct device *dev, struct clk_hw *hw)
3861 {
3862 struct clk *clk;
3863 int ret = clk_hw_register(dev, hw);
3864
3865 if (ret < 0)
3866 return ERR_PTR(ret);
3867
> 3868 clk = clk_hw_get_clk(hw);
3869 if (IS_ERR_OR_NULL(clk))
3870 clk_hw_unregister(hw);
3871
3872 return clk;
3873 }
3874 EXPORT_SYMBOL_GPL(clk_register);
3875
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 28007 bytes --]
next prev parent reply other threads:[~2020-05-20 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 17:07 [RFC PATCH] clk: rework clk_register to use the clk_hw API Jerome Brunet
2020-05-19 21:00 ` kbuild test robot
2020-05-20 0:24 ` kbuild test robot [this message]
2020-05-20 1:49 ` kbuild test robot
2020-11-14 21:02 ` Stephen Boyd
2020-11-16 15:13 ` Jerome Brunet
2020-11-18 1:43 ` Stephen Boyd
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=202005200802.CbKffDga%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.