From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kbuild-all@lists.01.org
Subject: Re: sound/soc/intel/catpt/loader.c:654 catpt_first_boot_firmware() warn: consider using resource_size() here
Date: Mon, 23 Nov 2020 12:53:17 +0200 [thread overview]
Message-ID: <20201123105317.GZ4077@smile.fi.intel.com> (raw)
In-Reply-To: <202011220325.oB7oeTEq-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Sun, Nov 22, 2020 at 03:52:27AM +0800, kernel test robot wrote:
> 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
...
> 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,
This sounds like false positive. From where it gets the idea of resource_size()
for the *start* offset?!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-11-23 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 19:52 sound/soc/intel/catpt/loader.c:654 catpt_first_boot_firmware() warn: consider using resource_size() here kernel test robot
2020-11-23 10:53 ` Andy Shevchenko [this message]
2020-11-23 11:41 ` Rojewski, Cezary
2020-11-24 8:00 ` Rong Chen
2020-11-24 9:13 ` Andy Shevchenko
2020-11-24 9:23 ` Rong Chen
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 11:28 kernel test robot
2020-12-21 11:59 kernel test robot
2020-12-21 14:51 kernel test robot
2020-12-22 20:53 kernel test robot
2021-04-16 2:41 kernel test robot
2021-08-05 16:54 kernel test robot
2021-09-29 3:56 kernel test robot
2024-12-03 1:02 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=20201123105317.GZ4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.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.