From: kernel test robot <lkp@intel.com>
To: James Morse <james.morse@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [morse:mpam/snapshot/v6.5-rc1 138/150] fs/resctrl/rdtgroup.c:850:24: error: implicit declaration of function 'iommu_get_group_kset'; did you mean 'iommu_group_get'?
Date: Sat, 26 Aug 2023 08:06:49 +0800 [thread overview]
Message-ID: <202308260737.qAn48aMP-lkp@intel.com> (raw)
Hi James,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git mpam/snapshot/v6.5-rc1
head: b35e256b516ef563cb57da2628dc19bcd600e35f
commit: 9e9af35cd8e4b32e9ccba2fa49c1ce600b3066b8 [138/150] fs/resctrl: Add support for assigning iommu_groups to resctrl groups
config: i386-buildonly-randconfig-005-20230826 (https://download.01.org/0day-ci/archive/20230826/202308260737.qAn48aMP-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230826/202308260737.qAn48aMP-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/202308260737.qAn48aMP-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
fs/resctrl/rdtgroup.c: In function 'show_rdt_iommu':
>> fs/resctrl/rdtgroup.c:850:24: error: implicit declaration of function 'iommu_get_group_kset'; did you mean 'iommu_group_get'? [-Werror=implicit-function-declaration]
850 | iommu_groups = iommu_get_group_kset();
| ^~~~~~~~~~~~~~~~~~~~
| iommu_group_get
>> fs/resctrl/rdtgroup.c:850:22: warning: assignment to 'struct kset *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
850 | iommu_groups = iommu_get_group_kset();
| ^
cc1: some warnings being treated as errors
vim +850 fs/resctrl/rdtgroup.c
839
840 static void show_rdt_iommu(struct rdtgroup *r, struct seq_file *s)
841 {
842 struct kset *iommu_groups;
843 struct iommu_group *group;
844 struct kobject *group_kobj = NULL;
845
846 if (!IS_ENABLED(CONFIG_RESCTRL_IOMMU) ||
847 !static_branch_unlikely(&resctrl_abi_playground))
848 return;
849
> 850 iommu_groups = iommu_get_group_kset();
851
852 while ((group_kobj = kset_get_next_obj(iommu_groups, group_kobj))) {
853
854 /* iommu_group_get_from_kobj() wants to drop a reference */
855 kobject_get(group_kobj);
856
857 group = iommu_group_get_from_kobj(group_kobj);
858 if (!group)
859 continue;
860
861 if (iommu_matches_rdtgroup(group, r))
862 seq_printf(s, "iommu_group:%s\n", group_kobj->name);
863 }
864
865 kset_put(iommu_groups);
866 }
867
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-26 0:07 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=202308260737.qAn48aMP-lkp@intel.com \
--to=lkp@intel.com \
--cc=james.morse@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.