mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [driver-core:driver-core-testing] BUILD SUCCESS 59789f3418dd3c0a187490d49e900a59a5c8d732
Date: Sun, 23 Oct 2022 14:33:40 +0200	[thread overview]
Message-ID: <Y1U0pINWo5yjUdc2@kroah.com> (raw)
In-Reply-To: <635484ed.ADi+2sBza+UlAhjj%lkp@intel.com>

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?

thanks,

greg k-h

       reply	other threads:[~2022-10-23 12:33 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 ` Greg Kroah-Hartman [this message]
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

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=Y1U0pINWo5yjUdc2@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --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
Powered by JetHome