[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1WZSysScBH0/6kd@smile.fi.intel.com>
Date: Sun, 23 Oct 2022 22:43:07 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: kernel test robot <lkp@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [driver-core:driver-core-testing] BUILD SUCCESS
59789f3418dd3c0a187490d49e900a59a5c8d732
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));
>
> Now that dev_fwnode() is an inline function, the compiler is confused as
> to what function to select? Maybe, I don't know, it seems odd, can you
> look into it?
Hmm... I can't reproduce on my side.
Any (additional) information about compiler, architecture, etc?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists