All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2] ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype
Date: Tue, 08 Feb 2022 18:44:51 +0800	[thread overview]
Message-ID: <202202081845.I5Ieercg-lkp@intel.com> (raw)
In-Reply-To: <20220103155838.616580-1-sudeep.holla@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]

Hi Sudeep,

I love your patch! Perhaps something to improve:

[auto build test WARNING on rafael-pm/linux-next]
[cannot apply to linux/master linus/master v5.17-rc3 next-20220208]
[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]

url:    https://github.com/0day-ci/linux/commits/Sudeep-Holla/ACPI-PCC-Implement-OperationRegion-handler-for-the-PCC-Type-3-subtype/20220104-000003
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20220208/202202081845.I5Ieercg-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/1dbcdc47eadc8c55659410fc03d067f3438a386a
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Sudeep-Holla/ACPI-PCC-Implement-OperationRegion-handler-for-the-PCC-Type-3-subtype/20220104-000003
        git checkout 1dbcdc47eadc8c55659410fc03d067f3438a386a
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/acpi/acpi_pcc.c:34:22: sparse: sparse: symbol 'pcc_ctx' was not declared. Should it be static?

vim +/pcc_ctx +34 drivers/acpi/acpi_pcc.c

    33	
  > 34	struct acpi_pcc_info pcc_ctx;
    35	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  parent reply	other threads:[~2022-02-08 10:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 15:58 [PATCH v2] ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype Sudeep Holla
2022-01-04  8:01 ` kernel test robot
2022-01-04  8:01   ` kernel test robot
2022-01-05 17:45 ` [RFC PATCH] ACPI: PCC: pcc_ctx can be static kernel test robot
2022-01-05 17:45   ` kernel test robot
2022-01-06 14:12   ` Sudeep Holla
2022-01-06 14:12     ` Sudeep Holla
2022-01-12 18:42     ` Rafael J. Wysocki
2022-01-12 18:42       ` Rafael J. Wysocki
2022-01-05 17:50 ` [PATCH v2] ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype kernel test robot
2022-01-05 17:50   ` kernel test robot
2022-01-05 21:46 ` kernel test robot
2022-01-05 21:46   ` kernel test robot
2022-01-13  8:45 ` kernel test robot
2022-01-20 11:04 ` kernel test robot
2022-01-25  6:11 ` kernel test robot
2022-02-07  6:16 ` kernel test robot
2022-02-08 10:44 ` kernel test robot [this message]
2022-02-08 10:52   ` Sudeep Holla

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=202202081845.I5Ieercg-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.