From: kernel test robot <lkp@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>,
intel-xe@lists.freedesktop.org, linux-acpi@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, anshuman.gupta@intel.com,
rafael@kernel.org, lenb@kernel.org, bhelgaas@google.com,
ilpo.jarvinen@linux.intel.com, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com, varun.gupta@intel.com,
ville.syrjala@linux.intel.com, uma.shankar@intel.com
Subject: Re: [PATCH v3 06/11] drm/xe/vrsr: Initialize VRSR feature
Date: Sat, 24 May 2025 05:33:30 +0800 [thread overview]
Message-ID: <202505240511.h1zy992X-lkp@intel.com> (raw)
In-Reply-To: <20250523190155.2623462-7-badal.nilawar@intel.com>
Hi Badal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on next-20250523]
[cannot apply to rafael-pm/linux-next rafael-pm/bleeding-edge pci/next pci/for-linus linus/master v6.15-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Badal-Nilawar/PCI-ACPI-Add-D3cold-Aux-Power-Limit_DSM-method/20250524-030125
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20250523190155.2623462-7-badal.nilawar%40intel.com
patch subject: [PATCH v3 06/11] drm/xe/vrsr: Initialize VRSR feature
config: arm-randconfig-002-20250524 (https://download.01.org/0day-ci/archive/20250524/202505240511.h1zy992X-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250524/202505240511.h1zy992X-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/202505240511.h1zy992X-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/xe/xe_device_types.h:10:0,
from drivers/gpu/drm/xe/xe_bo_types.h:16,
from drivers/gpu/drm/xe/xe_bo.h:11,
from drivers/gpu/drm/xe/xe_query.c:17:
>> include/linux/pci-acpi.h:149:12: warning: 'pci_acpi_add_perst_assertion_delay' defined but not used [-Wunused-function]
static int pci_acpi_add_perst_assertion_delay(struct pci_dev *dev, u32 delay_us)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/pci-acpi.h:143:12: warning: 'pci_acpi_request_d3cold_aux_power' defined but not used [-Wunused-function]
static int pci_acpi_request_d3cold_aux_power(struct pci_dev *dev, u32 requested_power,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/pci_acpi_add_perst_assertion_delay +149 include/linux/pci-acpi.h
ac1c8e35a3262d Kuppuswamy Sathyanarayanan 2020-03-23 134
59dc33252ee777 Rafael J. Wysocki 2021-08-24 135 int pci_acpi_set_companion_lookup_hook(struct acpi_device *(*func)(struct pci_dev *));
59dc33252ee777 Rafael J. Wysocki 2021-08-24 136 void pci_acpi_clear_companion_lookup_hook(void);
004b1d6651d930 Anshuman Gupta 2025-05-24 137 int pci_acpi_request_d3cold_aux_power(struct pci_dev *dev, u32 requested_power,
004b1d6651d930 Anshuman Gupta 2025-05-24 138 u32 *retry_interval);
57059451b12af0 Anshuman Gupta 2025-05-24 139 int pci_acpi_add_perst_assertion_delay(struct pci_dev *dev, u32 delay_us);
5090d4a6a1f150 Jiang Liu 2013-04-12 140 #else /* CONFIG_ACPI */
5090d4a6a1f150 Jiang Liu 2013-04-12 141 static inline void acpi_pci_add_bus(struct pci_bus *bus) { }
5090d4a6a1f150 Jiang Liu 2013-04-12 142 static inline void acpi_pci_remove_bus(struct pci_bus *bus) { }
004b1d6651d930 Anshuman Gupta 2025-05-24 @143 static int pci_acpi_request_d3cold_aux_power(struct pci_dev *dev, u32 requested_power,
004b1d6651d930 Anshuman Gupta 2025-05-24 144 u32 *retry_interval)
004b1d6651d930 Anshuman Gupta 2025-05-24 145 {
004b1d6651d930 Anshuman Gupta 2025-05-24 146 return -EOPNOTSUPP;
004b1d6651d930 Anshuman Gupta 2025-05-24 147 }
57059451b12af0 Anshuman Gupta 2025-05-24 148
57059451b12af0 Anshuman Gupta 2025-05-24 @149 static int pci_acpi_add_perst_assertion_delay(struct pci_dev *dev, u32 delay_us)
57059451b12af0 Anshuman Gupta 2025-05-24 150 {
57059451b12af0 Anshuman Gupta 2025-05-24 151 return -EOPNOTSUPP;
57059451b12af0 Anshuman Gupta 2025-05-24 152 }
5090d4a6a1f150 Jiang Liu 2013-04-12 153 #endif /* CONFIG_ACPI */
^1da177e4c3f41 Linus Torvalds 2005-04-16 154
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-23 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 19:01 [PATCH v3 00/11] VRAM Self Refresh Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 01/11] PCI/ACPI: Add D3cold Aux Power Limit_DSM method Badal Nilawar
2025-05-24 6:00 ` Sathyanarayanan Kuppuswamy
2025-05-29 6:18 ` Nilawar, Badal
2025-05-29 7:11 ` Nilawar, Badal
2025-05-23 19:01 ` [PATCH v3 02/11] PCI/ACPI: Per root port allow one Aux power limit request Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 03/11] PCI/ACPI: Add PERST# Assertion Delay _DSM method Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 04/11] drm/xe/vrsr: Introduce flag has_vrsr Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 05/11] drm/xe/vrsr: Detect VRSR Capability Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 06/11] drm/xe/vrsr: Initialize VRSR feature Badal Nilawar
2025-05-23 21:33 ` kernel test robot [this message]
2025-05-23 19:01 ` [PATCH v3 07/11] drm/xe/vrsr: Enable VRSR on default VGA boot device Badal Nilawar
2025-05-23 22:04 ` kernel test robot
2025-05-23 19:01 ` [PATCH v3 08/11] drm/xe/vrsr: Refactor d3cold.allowed to a enum Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 09/11] drm/xe/pm: D3Cold target state Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 10/11] drm/xe/vrsr: Enable VRSR Badal Nilawar
2025-05-23 19:01 ` [PATCH v3 11/11] drm/xe/vrsr: Introduce a debugfs node named vrsr_capable Badal Nilawar
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=202505240511.h1zy992X-lkp@intel.com \
--to=lkp@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=uma.shankar@intel.com \
--cc=varun.gupta@intel.com \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox