[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfxWwHja+QG-9Fhkh=6nd18RahgkS96SDL+y_uTR8o+jA@mail.gmail.com>
Date: Tue, 24 Nov 2020 11:13:06 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Rong Chen <rong.a.chen@...el.com>
Cc: "Rojewski, Cezary" <cezary.rojewski@...el.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
lkp <lkp@...el.com>,
"kbuild-all@...ts.01.org" <kbuild-all@...ts.01.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>
Subject: Re: [kbuild-all] Re: sound/soc/intel/catpt/loader.c:654
catpt_first_boot_firmware() warn: consider using resource_size() here
On Tue, Nov 24, 2020 at 10:06 AM Rong Chen <rong.a.chen@...el.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.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists