From: kernel test robot <lkp@intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: sound/soc/intel/catpt/loader.c:654 catpt_first_boot_firmware() warn: consider using resource_size() here
Date: Sun, 22 Nov 2020 03:52:27 +0800 [thread overview]
Message-ID: <202011220325.oB7oeTEq-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 27bba9c532a8d21050b94224ffd310ad0058c353
commit: 6cbfa11d2694b8a1e46d6834fb9705d5589e3ef1 ASoC: Intel: Select catpt and deprecate haswell
date: 7 weeks ago
config: x86_64-randconfig-m001-20201122 (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
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 637
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 638 int catpt_first_boot_firmware(struct catpt_dev *cdev)
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 639 {
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 640 struct resource *res;
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 641 int ret;
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 642
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 643 ret = catpt_boot_firmware(cdev, false);
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 644 if (ret) {
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 645 dev_err(cdev->dev, "basefw boot failed: %d\n", ret);
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 646 return ret;
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 647 }
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 648
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 649 /* restrict FW Core dump area */
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 650 __request_region(&cdev->dram, 0, 0x200, NULL, 0);
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 651 /* restrict entire area following BASE_FW - highest offset in DRAM */
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 652 for (res = cdev->dram.child; res->sibling; res = res->sibling)
a9aa6fb3eb6c7e Cezary Rojewski 2020-09-29 653 ;
a9aa6fb3eb6c7e 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: 36022 bytes --]
next reply other threads:[~2020-11-21 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 19:52 kernel test robot [this message]
2020-11-23 10:53 ` Andy Shevchenko
2020-11-23 11:41 ` Rojewski, Cezary
2020-11-24 8:00 ` [kbuild-all] " Rong Chen
2020-11-24 9:13 ` Andy Shevchenko
2020-11-24 9:23 ` Rong Chen
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=202011220325.oB7oeTEq-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-kernel@vger.kernel.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
all inboxes | Powered by JetHome®