From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Chen, Rong A" <rong.a.chen@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org, Dan Carpenter <error27@gmail.com>
Subject: Re: [driver-core:driver-core-testing] BUILD SUCCESS 59789f3418dd3c0a187490d49e900a59a5c8d732
Date: Mon, 24 Oct 2022 13:51:38 +0300 [thread overview]
Message-ID: <Y1ZuOg2b06u3TJtV@kadam> (raw)
In-Reply-To: <Y1ZZuY/cS/zePKTe@smile.fi.intel.com>
On Mon, Oct 24, 2022 at 12:24:09PM +0300, Andy Shevchenko wrote:
> On Mon, Oct 24, 2022 at 05:08:37PM +0800, Chen, Rong A wrote:
> > On 10/24/2022 4:57 PM, Andy Shevchenko wrote:
> > > On Mon, Oct 24, 2022 at 09:10:53AM +0800, Chen, Rong A wrote:
> > > > On 10/24/2022 3:52 AM, Andy Shevchenko wrote:
> > > > > On Sun, Oct 23, 2022 at 10:43:07PM +0300, Andy Shevchenko wrote:
> > > > > > On Sun, Oct 23, 2022 at 02:33:40PM +0200, Greg Kroah-Hartman wrote:
> > > > > > > On Sun, Oct 23, 2022 at 08:03:57AM +0800, kernel test robot wrote:
> > > > > > > > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git driver-core-testing
> > > > > > > > branch HEAD: 59789f3418dd3c0a187490d49e900a59a5c8d732 device property: Constify parameter in device_dma_supported() and device_get_dma_attr()
> > > > > > > >
> > > > > > > > Unverified Warning (likely false positive, please contact us if interested):
> > > > > > > >
> > > > > > > > drivers/hwmon/iio_hwmon.c:155 iio_hwmon_probe() warn: could not determine type of argument 4
> > > > > > >
> > > > > > > Andy, this is due to your changes, here's the offending code:
> > > > > > >
> > > > > > > sname = devm_kasprintf(dev, GFP_KERNEL, "%pfwP", dev_fwnode(dev));
> > > > > > >
[ snip ]
> >
> > Hi Andy,
> >
> > It's a smatch warning, it may be a false positive since Dan didn't forward
> > the report. +Dan
> >
> > smatch warnings:
> > drivers/hwmon/iio_hwmon.c:155 iio_hwmon_probe() warn: could not determine
> > type of argument 4
>
> Ah, okay, pretty much looks like false positive due to smatch unable to handle
> _Generic().
>
Yes. Thanks. I'm testing out a fix now.
It will take some days or a week before I push the fix probably because
I have a bunch of other changes I'm doing as well.
regards,
dan carpenter
prev parent reply other threads:[~2022-10-24 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <635484ed.ADi+2sBza+UlAhjj%lkp@intel.com>
2022-10-23 12:33 ` [driver-core:driver-core-testing] BUILD SUCCESS 59789f3418dd3c0a187490d49e900a59a5c8d732 Greg Kroah-Hartman
2022-10-23 19:43 ` Andy Shevchenko
2022-10-23 19:52 ` Andy Shevchenko
2022-10-24 1:10 ` Chen, Rong A
2022-10-24 8:57 ` Andy Shevchenko
2022-10-24 9:08 ` Chen, Rong A
2022-10-24 9:24 ` Andy Shevchenko
2022-10-24 10:51 ` Dan Carpenter [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=Y1ZuOg2b06u3TJtV@kadam \
--to=dan.carpenter@oracle.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rong.a.chen@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