All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Avadhut Naik <Avadhut.Naik@amd.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v3 3/3] ACPI: APEI: EINJ: Add support for vendor defined error types
Date: Tue, 13 Jun 2023 20:26:41 +0800	[thread overview]
Message-ID: <202306132042.TcLMMRQd-lkp@intel.com> (raw)
In-Reply-To: <20230612215139.5132-4-Avadhut.Naik@amd.com>

Hi Avadhut,

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

[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus linus/master v6.4-rc6 next-20230613]
[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/Avadhut-Naik/ACPI-APEI-EINJ-Refactor-available_error_type_show/20230613-055420
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link:    https://lore.kernel.org/r/20230612215139.5132-4-Avadhut.Naik%40amd.com
patch subject: [RFC PATCH v3 3/3] ACPI: APEI: EINJ: Add support for vendor defined error types
config: x86_64-randconfig-s022-20230611 (https://download.01.org/0day-ci/archive/20230613/202306132042.TcLMMRQd-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/intel-lab-lkp/linux/commit/9c7102f9dd11f4a4dde71e443eb91bf2cf9f4674
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Avadhut-Naik/ACPI-APEI-EINJ-Refactor-available_error_type_show/20230613-055420
        git checkout 9c7102f9dd11f4a4dde71e443eb91bf2cf9f4674
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 olddefconfig
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/acpi/apei/

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/202306132042.TcLMMRQd-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/acpi/apei/einj.c:195:36: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected void *static [toplevel] data @@     got void [noderef] __iomem * @@
   drivers/acpi/apei/einj.c:195:36: sparse:     expected void *static [toplevel] data
   drivers/acpi/apei/einj.c:195:36: sparse:     got void [noderef] __iomem *
   drivers/acpi/apei/einj.c:210:11: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct vendor_error_type_extension *v @@     got void [noderef] __iomem * @@
   drivers/acpi/apei/einj.c:210:11: sparse:     expected struct vendor_error_type_extension *v
   drivers/acpi/apei/einj.c:210:11: sparse:     got void [noderef] __iomem *
   drivers/acpi/apei/einj.c:219:29: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void [noderef] __iomem *virt @@     got struct vendor_error_type_extension *v @@
   drivers/acpi/apei/einj.c:219:29: sparse:     expected void [noderef] __iomem *virt
   drivers/acpi/apei/einj.c:219:29: sparse:     got struct vendor_error_type_extension *v
   drivers/acpi/apei/einj.c:245:25: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct set_error_type_with_address *v5param @@     got void [noderef] __iomem * @@
   drivers/acpi/apei/einj.c:245:25: sparse:     expected struct set_error_type_with_address *v5param
   drivers/acpi/apei/einj.c:245:25: sparse:     got void [noderef] __iomem *
   drivers/acpi/apei/einj.c:255:25: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct einj_parameter *v4param @@     got void [noderef] __iomem * @@
   drivers/acpi/apei/einj.c:255:25: sparse:     expected struct einj_parameter *v4param
   drivers/acpi/apei/einj.c:255:25: sparse:     got void [noderef] __iomem *
   drivers/acpi/apei/einj.c:259:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void [noderef] __iomem *virt @@     got struct einj_parameter *v4param @@
   drivers/acpi/apei/einj.c:259:45: sparse:     expected void [noderef] __iomem *virt
   drivers/acpi/apei/einj.c:259:45: sparse:     got struct einj_parameter *v4param
   drivers/acpi/apei/einj.c:326:21: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct acpi_einj_trigger *trigger_tab @@     got void [noderef] __iomem * @@
   drivers/acpi/apei/einj.c:326:21: sparse:     expected struct acpi_einj_trigger *trigger_tab
   drivers/acpi/apei/einj.c:326:21: sparse:     got void [noderef] __iomem *
   drivers/acpi/apei/einj.c:352:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *addr @@     got struct acpi_einj_trigger *trigger_tab @@
   drivers/acpi/apei/einj.c:352:17: sparse:     expected void volatile [noderef] __iomem *addr
   drivers/acpi/apei/einj.c:352:17: sparse:     got struct acpi_einj_trigger *trigger_tab
   drivers/acpi/apei/einj.c:353:21: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct acpi_einj_trigger *trigger_tab @@     got void [noderef] __iomem * @@
   drivers/acpi/apei/einj.c:353:21: sparse:     expected struct acpi_einj_trigger *trigger_tab
   drivers/acpi/apei/einj.c:353:21: sparse:     got void [noderef] __iomem *
   drivers/acpi/apei/einj.c:416:25: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *addr @@     got struct acpi_einj_trigger *trigger_tab @@
   drivers/acpi/apei/einj.c:416:25: sparse:     expected void volatile [noderef] __iomem *addr
   drivers/acpi/apei/einj.c:416:25: sparse:     got struct acpi_einj_trigger *trigger_tab
   drivers/acpi/apei/einj.c:817:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void [noderef] __iomem *virt @@     got void *static [assigned] [toplevel] einj_param @@
   drivers/acpi/apei/einj.c:817:37: sparse:     expected void [noderef] __iomem *virt
   drivers/acpi/apei/einj.c:817:37: sparse:     got void *static [assigned] [toplevel] einj_param
   drivers/acpi/apei/einj.c:819:58: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void [noderef] __iomem *virt @@     got void *static [addressable] [assigned] [toplevel] data @@
   drivers/acpi/apei/einj.c:819:58: sparse:     expected void [noderef] __iomem *virt
   drivers/acpi/apei/einj.c:819:58: sparse:     got void *static [addressable] [assigned] [toplevel] data

vim +195 drivers/acpi/apei/einj.c

   185	
   186	static void get_oem_vendor_struct(u64 paddr, int offset,
   187					  struct vendor_error_type_extension *v)
   188	{
   189		unsigned long vendor_size;
   190		u64 target_pa = paddr + offset + sizeof(struct vendor_error_type_extension);
   191	
   192		vendor_size = v->length - sizeof(struct vendor_error_type_extension);
   193	
   194		if (vendor_size)
 > 195			vendor_errors.data = acpi_os_map_iomem(target_pa, vendor_size);
   196	
   197		if (vendor_errors.data)
   198			vendor_errors.size = vendor_size;
   199	}
   200	

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

  reply	other threads:[~2023-06-13 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 21:51 [RFC PATCH v3 0/3] Add support for Vendor Defined Error Types in Einj Module Avadhut Naik
2023-06-12 21:51 ` [RFC PATCH v3 1/3] ACPI: APEI: EINJ: Refactor available_error_type_show() Avadhut Naik
2023-06-12 21:51 ` [RFC PATCH v3 2/3] fs: debugfs: Add write functionality to debugfs blobs Avadhut Naik
2023-06-13  7:59   ` Greg KH
2023-06-13 10:05     ` Alexey Kardashevskiy
2023-06-13 10:22       ` Greg KH
2023-06-13 22:35         ` Avadhut Naik
2023-06-12 21:51 ` [RFC PATCH v3 3/3] ACPI: APEI: EINJ: Add support for vendor defined error types Avadhut Naik
2023-06-13 12:26   ` kernel test robot [this message]
2023-06-13  8:01 ` [RFC PATCH v3 0/3] Add support for Vendor Defined Error Types in Einj Module Greg KH
2023-06-13 22:34   ` Avadhut Naik

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=202306132042.TcLMMRQd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Avadhut.Naik@amd.com \
    --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.