All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC 1/6] PCI/ACPI: Implement PCI FW _DSM method
Date: Tue, 25 Feb 2025 07:13:34 +0800	[thread overview]
Message-ID: <202502250636.OtsWH8Fp-lkp@intel.com> (raw)
In-Reply-To: <20250224164849.3746751-2-anshuman.gupta@intel.com>

Hi Anshuman,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on rafael-pm/linux-next rafael-pm/bleeding-edge pci/next pci/for-linus linus/master v6.14-rc4 next-20250224]
[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/Anshuman-Gupta/PCI-ACPI-Implement-PCI-FW-_DSM-method/20250225-005537
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:    https://lore.kernel.org/r/20250224164849.3746751-2-anshuman.gupta%40intel.com
patch subject: [RFC 1/6] PCI/ACPI: Implement PCI FW _DSM method
config: arm64-randconfig-003-20250225 (https://download.01.org/0day-ci/archive/20250225/202502250636.OtsWH8Fp-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250225/202502250636.OtsWH8Fp-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/202502250636.OtsWH8Fp-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/pci/controller/pci-xgene.c:19:
>> include/linux/pci-acpi.h:143:5: warning: no previous prototype for function 'pci_acpi_request_d3cold_aux_power' [-Wmissing-prototypes]
   int pci_acpi_request_d3cold_aux_power(struct pci_dev *dev, u32 requested_power)
       ^
   include/linux/pci-acpi.h:143:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   int pci_acpi_request_d3cold_aux_power(struct pci_dev *dev, u32 requested_power)
   ^
   static 
>> include/linux/pci-acpi.h:148:5: warning: no previous prototype for function 'pci_acpi_add_perst_assertion_delay' [-Wmissing-prototypes]
   int pci_acpi_add_perst_assertion_delay(struct pci_dev *dev, u32 delay_us)
       ^
   include/linux/pci-acpi.h:148:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   int pci_acpi_add_perst_assertion_delay(struct pci_dev *dev, u32 delay_us)
   ^
   static 
   2 warnings generated.


vim +/pci_acpi_request_d3cold_aux_power +143 include/linux/pci-acpi.h

   139	
   140	#else	/* CONFIG_ACPI */
   141	static inline void acpi_pci_add_bus(struct pci_bus *bus) { }
   142	static inline void acpi_pci_remove_bus(struct pci_bus *bus) { }
 > 143	int pci_acpi_request_d3cold_aux_power(struct pci_dev *dev, u32 requested_power)
   144	{
   145		return -EOPNOTSUPP;
   146	}
   147	
 > 148	int pci_acpi_add_perst_assertion_delay(struct pci_dev *dev, u32 delay_us)
   149	{
   150		return -EOPNOTSUPP;
   151	}
   152	#endif	/* CONFIG_ACPI */
   153	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-02-24 23:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 16:48 [RFC 0/6] VRAM Self Refresh Anshuman Gupta
2025-02-24 16:48 ` [RFC 1/6] PCI/ACPI: Implement PCI FW _DSM method Anshuman Gupta
2025-02-24 19:40   ` Bjorn Helgaas
2025-02-25 18:25     ` Gupta, Anshuman
2025-02-25 20:30       ` Bjorn Helgaas
2025-02-24 23:13   ` kernel test robot [this message]
2025-02-24 16:48 ` [RFC 2/6] drm/xe/vrsr: Detect vrsr capability Anshuman Gupta
2025-03-07 21:50   ` Rodrigo Vivi
2025-02-24 16:48 ` [RFC 3/6] drm/xe/vrsr: Apis to init and enable VRSR feature Anshuman Gupta
2025-02-24 19:43   ` Bjorn Helgaas
2025-02-26  5:21   ` kernel test robot
2025-02-26 11:51   ` kernel test robot
2025-03-10 17:23   ` Rodrigo Vivi
2025-02-24 16:48 ` [RFC 4/6] drm/xe/vrsr: Refactor d3cold.allowed to a enum Anshuman Gupta
2025-03-10 17:28   ` Rodrigo Vivi
2025-04-01  5:24     ` Poosa, Karthik
2025-02-24 16:48 ` [RFC 5/6] drm/xe/pm: D3Cold target state Anshuman Gupta
2025-02-24 19:45   ` Bjorn Helgaas
2025-02-24 21:14   ` kernel test robot
2025-02-24 21:37   ` kernel test robot
2025-02-25 17:49   ` Ville Syrjälä
2025-02-25 18:00     ` Gupta, Anshuman
2025-02-25 18:44       ` Ville Syrjälä
2025-02-24 16:48 ` [RFC 6/6] drm/xe/vrsr: Enable VRSR Anshuman Gupta
2025-04-01  5:19   ` [RFC,6/6] " Poosa, Karthik
2025-02-25  0:07 ` ✓ CI.Patch_applied: success for VRAM Self Refresh Patchwork
2025-02-25  0:08 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-25  0:08 ` ✗ CI.KUnit: failure " Patchwork

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=202502250636.OtsWH8Fp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=llvm@lists.linux.dev \
    --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.