linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Mark Brown <broonie@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [linux-next:master 12312/14891] sound/soc/intel/catpt/loader.c:654 catpt_first_boot_firmware() warn: consider using resource_size() here
Date: Thu, 15 Oct 2020 00:12:30 +0800	[thread overview]
Message-ID: <202010150027.VlbKtbYJ-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   f2fb1afc57304f9dd68c20a08270e287470af2eb
commit: 6cbfa11d2694b8a1e46d6834fb9705d5589e3ef1 [12312/14891] ASoC: Intel: Select catpt and deprecate haswell
config: x86_64-randconfig-m031-20201014 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0

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

smatch warnings:
sound/soc/intel/catpt/loader.c:654 catpt_first_boot_firmware() warn: consider using resource_size() here

vim +654 sound/soc/intel/catpt/loader.c

a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  637  
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  638  int catpt_first_boot_firmware(struct catpt_dev *cdev)
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  639  {
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  640  	struct resource *res;
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  641  	int ret;
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  642  
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  643  	ret = catpt_boot_firmware(cdev, false);
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  644  	if (ret) {
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  645  		dev_err(cdev->dev, "basefw boot failed: %d\n", ret);
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  646  		return ret;
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  647  	}
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  648  
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  649  	/* restrict FW Core dump area */
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  650  	__request_region(&cdev->dram, 0, 0x200, NULL, 0);
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  651  	/* restrict entire area following BASE_FW - highest offset in DRAM */
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  652  	for (res = cdev->dram.child; res->sibling; res = res->sibling)
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29  653  		;
a9aa6fb3eb6c7e0 Cezary Rojewski 2020-09-29 @654  	__request_region(&cdev->dram, res->end + 1,

:::::: The code at line 654 was first introduced by commit
:::::: a9aa6fb3eb6c7e0e7e117b3f2dfafef8c45b9ea6 ASoC: Intel: catpt: Firmware loading and context restore

:::::: TO: Cezary Rojewski <cezary.rojewski@intel.com>
:::::: CC: Mark Brown <broonie@kernel.org>

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33580 bytes --]

                 reply	other threads:[~2020-10-14 16:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202010150027.VlbKtbYJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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