From: kernel test robot <lkp@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [krzk-github:n/qcom-ufs-opp-v2 19/20] drivers/opp/core.c:898:33: error: 'const struct opp_table' has no member named 'clk'; did you mean 'clks'?
Date: Fri, 8 Apr 2022 05:33:06 +0800 [thread overview]
Message-ID: <202204080548.RCEpmt1c-lkp@intel.com> (raw)
tree: https://github.com/krzk/linux n/qcom-ufs-opp-v2
head: e10a6c68219eb9b5d79c2f447d8df698c38e5853
commit: ea240d6e8f1e8a618de2d76ff2e89a1cc3d39971 [19/20] pm wip
config: x86_64-randconfig-a002 (https://download.01.org/0day-ci/archive/20220408/202204080548.RCEpmt1c-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
# https://github.com/krzk/linux/commit/ea240d6e8f1e8a618de2d76ff2e89a1cc3d39971
git remote add krzk-github https://github.com/krzk/linux
git fetch --no-tags krzk-github n/qcom-ufs-opp-v2
git checkout ea240d6e8f1e8a618de2d76ff2e89a1cc3d39971
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/opp/core.c: In function '_set_opp_custom':
>> drivers/opp/core.c:898:33: error: 'const struct opp_table' has no member named 'clk'; did you mean 'clks'?
898 | data->clk = (opp_table->clk ? opp_table->clks[0] : NULL);
| ^~~
| clks
vim +898 drivers/opp/core.c
875
876 static int _set_opp_custom(const struct opp_table *opp_table,
877 struct device *dev, struct dev_pm_opp *opp,
878 unsigned long freq)
879 {
880 struct dev_pm_set_opp_data *data = opp_table->set_opp_data;
881 struct dev_pm_opp *old_opp = opp_table->current_opp;
882 int size;
883
884 /*
885 * We support this only if dev_pm_opp_set_regulators() was called
886 * earlier.
887 */
888 if (opp_table->sod_supplies) {
889 size = sizeof(*old_opp->supplies) * opp_table->regulator_count;
890 memcpy(data->old_opp.supplies, old_opp->supplies, size);
891 memcpy(data->new_opp.supplies, opp->supplies, size);
892 data->regulator_count = opp_table->regulator_count;
893 } else {
894 data->regulator_count = 0;
895 }
896
897 data->regulators = opp_table->regulators;
> 898 data->clk = (opp_table->clk ? opp_table->clks[0] : NULL);
899 data->dev = dev;
900 data->old_opp.rate = old_opp->rate;
901 data->new_opp.rate = freq;
902
903 return opp_table->set_opp(data);
904 }
905
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-07 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202204080548.RCEpmt1c-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.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