From: kernel test robot <lkp@intel.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [linux-next:master 3286/3636] drivers/cpufreq/mediatek-cpufreq.c:741:34: warning: 'mtk_cpufreq_machines' defined but not used
Date: Fri, 9 Aug 2024 07:08:16 +0800 [thread overview]
Message-ID: <202408090714.wcrqU6Pk-lkp@intel.com> (raw)
Hi Rob,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 222a3380f92b8791d4eeedf7cd750513ff428adf
commit: c7582ec853427c895d990e0244f19fe22b44a366 [3286/3636] cpufreq: Drop CONFIG_ARM and CONFIG_ARM64 dependency on Arm drivers
config: sh-randconfig-r123-20240808 (https://download.01.org/0day-ci/archive/20240809/202408090714.wcrqU6Pk-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240809/202408090714.wcrqU6Pk-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/202408090714.wcrqU6Pk-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cpufreq/mediatek-cpufreq.c:741:34: warning: 'mtk_cpufreq_machines' defined but not used [-Wunused-const-variable=]
741 | static const struct of_device_id mtk_cpufreq_machines[] __initconst = {
| ^~~~~~~~~~~~~~~~~~~~
vim +/mtk_cpufreq_machines +741 drivers/cpufreq/mediatek-cpufreq.c
d3296bb4cafd4b drivers/cpufreq/mediatek-cpufreq.c Jia-Wei Chang 2023-03-24 739
cf9a2438257da2 drivers/cpufreq/mt8173-cpufreq.c Daniel Kurtz 2017-03-02 740 /* List of machines supported by this driver */
862e0104f4d1a4 drivers/cpufreq/mediatek-cpufreq.c Sean Wang 2017-08-09 @741 static const struct of_device_id mtk_cpufreq_machines[] __initconst = {
ead858bd128d4e drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 742 { .compatible = "mediatek,mt2701", .data = &mt2701_platform_data },
ead858bd128d4e drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 743 { .compatible = "mediatek,mt2712", .data = &mt2701_platform_data },
0883426fd07e39 drivers/cpufreq/mediatek-cpufreq.c AngeloGioacchino Del Regno 2023-03-24 744 { .compatible = "mediatek,mt7622", .data = &mt7622_platform_data },
f85534113f5ae9 drivers/cpufreq/mediatek-cpufreq.c Daniel Golle 2023-06-05 745 { .compatible = "mediatek,mt7623", .data = &mt7623_platform_data },
b69ec356db1a7c drivers/cpufreq/mediatek-cpufreq.c Sam Shih 2024-04-19 746 { .compatible = "mediatek,mt7988a", .data = &mt7988_platform_data },
d3296bb4cafd4b drivers/cpufreq/mediatek-cpufreq.c Jia-Wei Chang 2023-03-24 747 { .compatible = "mediatek,mt8167", .data = &mt8516_platform_data },
ead858bd128d4e drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 748 { .compatible = "mediatek,mt817x", .data = &mt2701_platform_data },
ead858bd128d4e drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 749 { .compatible = "mediatek,mt8173", .data = &mt2701_platform_data },
ead858bd128d4e drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 750 { .compatible = "mediatek,mt8176", .data = &mt2701_platform_data },
0daa47325baee6 drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 751 { .compatible = "mediatek,mt8183", .data = &mt8183_platform_data },
39b360102f3ac6 drivers/cpufreq/mediatek-cpufreq.c Jia-Wei Chang 2022-05-05 752 { .compatible = "mediatek,mt8186", .data = &mt8186_platform_data },
ead858bd128d4e drivers/cpufreq/mediatek-cpufreq.c Rex-BC Chen 2022-05-05 753 { .compatible = "mediatek,mt8365", .data = &mt2701_platform_data },
d3296bb4cafd4b drivers/cpufreq/mediatek-cpufreq.c Jia-Wei Chang 2023-03-24 754 { .compatible = "mediatek,mt8516", .data = &mt8516_platform_data },
cf9a2438257da2 drivers/cpufreq/mt8173-cpufreq.c Daniel Kurtz 2017-03-02 755 { }
cf9a2438257da2 drivers/cpufreq/mt8173-cpufreq.c Daniel Kurtz 2017-03-02 756 };
af6eca06501118 drivers/cpufreq/mediatek-cpufreq.c Pali Rohár 2020-11-03 757 MODULE_DEVICE_TABLE(of, mtk_cpufreq_machines);
cf9a2438257da2 drivers/cpufreq/mt8173-cpufreq.c Daniel Kurtz 2017-03-02 758
:::::: The code at line 741 was first introduced by commit
:::::: 862e0104f4d1a489517cb1075ce974c0a1fd5a97 cpufreq: mediatek: add cleanups with the more generic naming
:::::: TO: Sean Wang <sean.wang@mediatek.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-08 23:08 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=202408090714.wcrqU6Pk-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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