From: kernel test robot <lkp@intel.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: oe-kbuild-all@lists.linux.dev, Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_misc_fixes_v1 38/59] include/linux/acpi_rimt.h:9:80: warning: 'struct iommu_ops' declared inside parameter list will not be visible outside of this definition or declaration
Date: Wed, 5 Feb 2025 02:39:31 +0800 [thread overview]
Message-ID: <202502050203.BfcAxUa6-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_misc_fixes_v1
head: 65e185d21a77888b7620a36702a81f2e6c27164a
commit: 544db00508e971a1352eab4881a73ece81c49540 [38/59] IOMMU: RISC-V: ACPI: Register IOMMU
config: riscv-alldefconfig (https://download.01.org/0day-ci/archive/20250205/202502050203.BfcAxUa6-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250205/202502050203.BfcAxUa6-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/202502050203.BfcAxUa6-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/iommu/riscv/iommu.c:16:
>> include/linux/acpi_rimt.h:9:80: warning: 'struct iommu_ops' declared inside parameter list will not be visible outside of this definition or declaration
9 | int rimt_iommu_configure_id(struct device *dev, const u32 *id_in, const struct iommu_ops *ops);
| ^~~~~~~~~
vim +9 include/linux/acpi_rimt.h
3dafa382fb9e96 Sunil V L 2024-08-16 @9 int rimt_iommu_configure_id(struct device *dev, const u32 *id_in, const struct iommu_ops *ops);
:::::: The code at line 9 was first introduced by commit
:::::: 3dafa382fb9e96e142e0171bf1d49ffc34ad13ea RISC-V: IOMMU: Add ACPI support using RIMT
:::::: TO: Sunil V L <sunilvl@ventanamicro.com>
:::::: CC: Anup Patel <anup@brainfault.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-04 18:39 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=202502050203.BfcAxUa6-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sunilvl@ventanamicro.com \
/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.