public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Petr Pavlu <petr.pavlu@suse.com>,
	rafael@kernel.org, lenb@kernel.org, viresh.kumar@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, pmladek@suse.com,
	mcgrof@kernel.org, linux-acpi@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Petr Pavlu <petr.pavlu@suse.com>
Subject: Re: [PATCH v3] ACPI: cpufreq: use a platform device to load ACPI PPC and PCC drivers
Date: Thu, 2 Mar 2023 07:48:11 +0800	[thread overview]
Message-ID: <202303020759.pwVPib0p-lkp@intel.com> (raw)
In-Reply-To: <20230301085717.10411-1-petr.pavlu@suse.com>

Hi Petr,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on linus/master v6.2 next-20230301]
[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/Petr-Pavlu/ACPI-cpufreq-use-a-platform-device-to-load-ACPI-PPC-and-PCC-drivers/20230301-165927
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link:    https://lore.kernel.org/r/20230301085717.10411-1-petr.pavlu%40suse.com
patch subject: [PATCH v3] ACPI: cpufreq: use a platform device to load ACPI PPC and PCC drivers
config: ia64-allyesconfig (https://download.01.org/0day-ci/archive/20230302/202303020759.pwVPib0p-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/59eb26f9b02165cc5c5fb6514ff4d2a8d7a91356
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Petr-Pavlu/ACPI-cpufreq-use-a-platform-device-to-load-ACPI-PPC-and-PCC-drivers/20230301-165927
        git checkout 59eb26f9b02165cc5c5fb6514ff4d2a8d7a91356
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303020759.pwVPib0p-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/acpi/acpi_processor.c:177:13: warning: no previous prototype for 'acpi_pcc_cpufreq_init' [-Wmissing-prototypes]
     177 | void __init acpi_pcc_cpufreq_init(void) {}
         |             ^~~~~~~~~~~~~~~~~~~~~


vim +/acpi_pcc_cpufreq_init +177 drivers/acpi/acpi_processor.c

   162	
   163	#ifdef CONFIG_X86
   164	/* Check presence of Processor Clocking Control by searching for \_SB.PCCH. */
   165	void __init acpi_pcc_cpufreq_init(void)
   166	{
   167		acpi_status status;
   168		acpi_handle handle;
   169	
   170		status = acpi_get_handle(NULL, "\\_SB", &handle);
   171		if (ACPI_FAILURE(status))
   172			return;
   173		if (acpi_has_method(handle, "PCCH"))
   174			cpufreq_add_device("pcc-cpufreq");
   175	}
   176	#else
 > 177	void __init acpi_pcc_cpufreq_init(void) {}
   178	#endif /* CONFIG_X86 */
   179	

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

      reply	other threads:[~2023-03-01 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  8:57 [PATCH v3] ACPI: cpufreq: use a platform device to load ACPI PPC and PCC drivers Petr Pavlu
2023-03-01 23:48 ` kernel test robot [this message]

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=202303020759.pwVPib0p-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=petr.pavlu@suse.com \
    --cc=pmladek@suse.com \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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