From: kernel test robot <lkp@intel.com>
To: Marek Vasut <marex@denx.de>, linux-clk@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Marek Vasut <marex@denx.de>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-power@fi.rohmeurope.com
Subject: Re: [PATCH 2/3] clk: Introduce 'critical-clocks' property
Date: Tue, 15 Feb 2022 21:57:16 +0800 [thread overview]
Message-ID: <202202152152.8a7M9Tkv-lkp@intel.com> (raw)
In-Reply-To: <20220215084412.8090-2-marex@denx.de>
Hi Marek,
I love your patch! Perhaps something to improve:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on v5.17-rc4 next-20220215]
[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]
url: https://github.com/0day-ci/linux/commits/Marek-Vasut/dt-bindings-clk-Introduce-critical-clocks-property/20220215-164757
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: x86_64-randconfig-a002-20220214 (https://download.01.org/0day-ci/archive/20220215/202202152152.8a7M9Tkv-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 37f422f4ac31c8b8041c6b62065263314282dab6)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/aded04bc3dec13df3f940621d94d84e32ff8a5ea
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Marek-Vasut/dt-bindings-clk-Introduce-critical-clocks-property/20220215-164757
git checkout aded04bc3dec13df3f940621d94d84e32ff8a5ea
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/clk/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/clk/clk.c:3881:6: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
int ret, i, index;
^
1 warning generated.
vim +/ret +3881 drivers/clk/clk.c
3874
3875 static void
3876 __clk_register_critical_clock(struct device_node *np, struct clk_core *core,
3877 struct clk_hw *hw)
3878 {
3879 struct of_phandle_args clkspec;
3880 u32 clksize, clktotal;
> 3881 int ret, i, index;
3882
3883 if (!np)
3884 return;
3885
3886 if (!core->ops->match_clkspec)
3887 return;
3888
3889 if (of_property_read_u32(np, "#clock-cells", &clksize))
3890 return;
3891
3892 /* Clock node with #clock-cells = <0> uses critical-clocks; */
3893 if (clksize == 0) {
3894 if (of_property_read_bool(np, "critical-clocks") &&
3895 !core->ops->match_clkspec(hw, &clkspec))
3896 core->flags |= CLK_IS_CRITICAL;
3897 return;
3898 }
3899
3900 clkspec.np = np;
3901 clktotal = of_property_count_u32_elems(np, "critical-clocks");
3902 clktotal /= clksize;
3903 for (index = 0; index < clktotal; index++) {
3904 for (i = 0; i < clksize; i++) {
3905 ret = of_property_read_u32_index(np, "critical-clocks",
3906 (index * clksize) + i,
3907 &(clkspec.args[i]));
3908 }
3909 if (!core->ops->match_clkspec(hw, &clkspec))
3910 core->flags |= CLK_IS_CRITICAL;
3911 }
3912 }
3913
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-02-15 13:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:44 [PATCH 1/3] dt-bindings: clk: Introduce 'critical-clocks' property Marek Vasut
2022-02-15 8:44 ` [PATCH 2/3] " Marek Vasut
2022-02-15 11:23 ` kernel test robot
2022-02-15 13:57 ` kernel test robot [this message]
2022-02-16 12:06 ` Vaittinen, Matti
2022-02-16 16:52 ` Marek Vasut
2022-02-17 5:01 ` Vaittinen, Matti
2022-02-17 13:43 ` Marek Vasut
2022-02-17 22:23 ` Stephen Boyd
2022-02-21 0:58 ` Marek Vasut
2022-03-09 20:54 ` Marek Vasut
2022-03-12 5:04 ` Stephen Boyd
2022-03-12 10:26 ` Marek Vasut
2022-03-15 23:52 ` Stephen Boyd
2022-03-16 11:30 ` Marek Vasut
2022-05-03 19:17 ` Marek Vasut
2022-02-15 8:44 ` [PATCH 3/3] clk: bd718xx: Implement basic .match_clkspec Marek Vasut
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=202202152152.8a7M9Tkv-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-power@fi.rohmeurope.com \
--cc=llvm@lists.linux.dev \
--cc=marex@denx.de \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).