From: Rong Chen <rong.a.chen@intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Dan Carpenter <error27@gmail.com>
Cc: "Rojewski, Cezary" <cezary.rojewski@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
lkp <lkp@intel.com>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [kbuild-all] Re: sound/soc/intel/catpt/loader.c:654 catpt_first_boot_firmware() warn: consider using resource_size() here
Date: Tue, 24 Nov 2020 17:23:09 +0800 [thread overview]
Message-ID: <aa75e040-7ead-6328-d148-0cbcbc8c89c1@intel.com> (raw)
In-Reply-To: <CAHp75VfxWwHja+QG-9Fhkh=6nd18RahgkS96SDL+y_uTR8o+jA@mail.gmail.com>
On 11/24/20 5:13 PM, Andy Shevchenko wrote:
> On Tue, Nov 24, 2020 at 10:06 AM Rong Chen <rong.a.chen@intel.com> wrote:
>> On 11/23/20 7:41 PM, Rojewski, Cezary wrote:
>>> On 2020-11-23 11:53 AM, Andy Shevchenko wrote:
>>>> On Sun, Nov 22, 2020 at 03:52:27AM +0800, kernel test robot wrote:
> ...
>
>>>> This sounds like false positive. From where it gets the idea of resource_size()
>>>> for the *start* offset?!
>>>>
>>> Indeed it is false positive. I've already explained this in:
>>>
>>> RE: [bug report] ASoC: Intel: catpt: Firmware loading and context restore
>>> https://www.spinics.net/lists/alsa-devel/msg117145.html
>> Thanks a lot, we'll ignore the warning next time.
> I think the proper solution here is to notify smatch upstream to fix the tool.
>
+Dan Carpenter
Hi Dan,
Could you take a look at this? the original report is at
https://lore.kernel.org/lkml/202011220325.oB7oeTEq-lkp@intel.com/
Best Regards,
Rong Chen
prev parent reply other threads:[~2020-11-24 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 19:52 kernel test robot
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 [this message]
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=aa75e040-7ead-6328-d148-0cbcbc8c89c1@intel.com \
--to=rong.a.chen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=error27@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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®