From: kernel test robot <lkp@intel.com>
To: Elena Reshetova <elena.reshetova@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: [intel-tdx:guest-filter 30/34] drivers/acpi/osl.c:410: warning: cannot understand function prototype: 'void *__ref acpi_os_map_memory_opregion(acpi_physical_address phys, acpi_size size) '
Date: Tue, 22 Aug 2023 04:54:47 +0800 [thread overview]
Message-ID: <202308220403.Cnc4i2d5-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git guest-filter
head: f84bcdf50d1bb34ff2715bb067074582b407f3d9
commit: 7be70dd0f99a936b19893afa9b0719009181bd34 [30/34] acpica: add acpi_os_map_memory_opregion
config: i386-randconfig-001-20230821 (https://download.01.org/0day-ci/archive/20230822/202308220403.Cnc4i2d5-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230822/202308220403.Cnc4i2d5-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/202308220403.Cnc4i2d5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/acpi/osl.c:410: warning: cannot understand function prototype: 'void *__ref acpi_os_map_memory_opregion(acpi_physical_address phys, acpi_size size) '
vim +410 drivers/acpi/osl.c
391
392 /**
393 * acpi_os_map_memory_opregion - Get a virtual address for a given physical
394 * address range. This function is intended to be used only for AML operation
395 * regions. In a confidential computing guest such regions needs to be explicitly
396 * shared with the host to avoid breaking the communication.
397 *
398 * @phys: Start of the physical address range to map.
399 * @size: Size of the physical address range to map.
400 *
401 * Look up the given physical address range in the list of existing ACPI memory
402 * mappings. If found, get a reference to it and return a pointer to it (its
403 * virtual address). If not found, map it, add it to that list and return a
404 * pointer to it.
405 *
406 * During early init (when acpi_permanent_mmap has not been set yet) this
407 * routine simply calls __acpi_map_table() to get the job done.
408 */
409 void *__ref acpi_os_map_memory_opregion(acpi_physical_address phys, acpi_size size)
> 410 {
411 if (!cc_platform_has(CC_ATTR_GUEST_MEM_ENCRYPT))
412 return (void *)__acpi_os_map_iomem(phys, size, false);
413 else
414 return (void *)__acpi_os_map_iomem(phys, size, true);
415 }
416 EXPORT_SYMBOL_GPL(acpi_os_map_memory_opregion);
417
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-21 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 20:54 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-03 10:25 [intel-tdx:guest-filter 30/34] drivers/acpi/osl.c:410: warning: cannot understand function prototype: 'void *__ref acpi_os_map_memory_opregion(acpi_physical_address phys, acpi_size size) ' kernel test robot
2023-08-18 5:03 kernel test robot
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=202308220403.Cnc4i2d5-lkp@intel.com \
--to=lkp@intel.com \
--cc=elena.reshetova@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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.