oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sudan Landge <sudanl@amazon.com>,
	tytso@mit.edu, Jason@zx2c4.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	sathyanarayanan.kuppuswamy@linux.intel.com,
	thomas.lendacky@amd.com, dan.j.williams@intel.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, graf@amazon.de, dwmw@amazon.co.uk,
	bchalios@amazon.es, xmarcalx@amazon.co.uk
Subject: Re: [PATCH v2 4/4] virt: vmgenid: add support for devicetree bindings
Date: Fri, 22 Mar 2024 03:52:32 +0800	[thread overview]
Message-ID: <202403220322.EGtpD4Jw-lkp@intel.com> (raw)
In-Reply-To: <20240321025105.53210-5-sudanl@amazon.com>

Hi Sudan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on a4145ce1e7bc247fd6f2846e8699473448717b37]

url:    https://github.com/intel-lab-lkp/linux/commits/Sudan-Landge/virt-vmgenid-rearrange-code-to-make-review-easier/20240321-105317
base:   a4145ce1e7bc247fd6f2846e8699473448717b37
patch link:    https://lore.kernel.org/r/20240321025105.53210-5-sudanl%40amazon.com
patch subject: [PATCH v2 4/4] virt: vmgenid: add support for devicetree bindings
config: x86_64-randconfig-123-20240321 (https://download.01.org/0day-ci/archive/20240322/202403220322.EGtpD4Jw-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240322/202403220322.EGtpD4Jw-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/202403220322.EGtpD4Jw-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/virt/vmgenid.c:153:43: sparse: sparse: cast removes address space '__iomem' of expression

vim +/__iomem +153 drivers/virt/vmgenid.c

   133	
   134	static int vmgenid_add_of(struct device *dev, struct vmgenid_state *state)
   135	{
   136	#ifdef	CONFIG_OF
   137		struct resource res;
   138		int ret = 0;
   139	
   140		if (of_address_to_resource(dev->of_node, 0, &res)) {
   141			dev_err(dev, "Failed to get resources from device tree");
   142			ret = -EINVAL;
   143			goto out;
   144		}
   145	
   146		if (!__request_mem_region(res.start, resource_size(&res),
   147					  "vmgenid", IORESOURCE_EXCLUSIVE)) {
   148			dev_err(dev, "Failed to request mem region");
   149			ret = -EINVAL;
   150			goto out;
   151		}
   152	
 > 153		ret = setup_vmgenid_state(state, (u8 *)of_iomap(dev->of_node, 0));
   154		if (ret)
   155			goto out;
   156	
   157		state->irq = irq_of_parse_and_map(dev->of_node, 0);
   158		dev->driver_data = state;
   159	
   160		if (request_irq(state->irq, vmgenid_of_irq_handler,
   161				IRQF_SHARED, "vmgenid", dev) < 0) {
   162			dev_err(dev, "request_irq failed");
   163			dev->driver_data = NULL;
   164			ret = -EINVAL;
   165			goto out;
   166		}
   167	
   168	out:
   169		return ret;
   170	#else
   171		(void)dev;
   172		(void)state;
   173		return -EINVAL;
   174	#endif
   175	}
   176	

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

       reply	other threads:[~2024-03-21 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321025105.53210-5-sudanl@amazon.com>
2024-03-21 19:52 ` kernel test robot [this message]
2024-03-22  8:02 ` [PATCH v2 4/4] virt: vmgenid: add support for devicetree bindings kernel test robot

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=202403220322.EGtpD4Jw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jason@zx2c4.com \
    --cc=bchalios@amazon.es \
    --cc=conor+dt@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw@amazon.co.uk \
    --cc=graf@amazon.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh+dt@kernel.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=sudanl@amazon.com \
    --cc=thomas.lendacky@amd.com \
    --cc=tytso@mit.edu \
    --cc=xmarcalx@amazon.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).