public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: kbuild-all@01.org, "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Ferry Toth <fntoth@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v1] ACPI / platform: Unregister stale platform devices
Date: Mon, 2 Sep 2019 15:19:11 +0800	[thread overview]
Message-ID: <201909021519.YR3Jdy5T%lkp@intel.com> (raw)
In-Reply-To: <20190830143432.21695-1-andriy.shevchenko@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

Hi Andy,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc6 next-20190830]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Andy-Shevchenko/ACPI-platform-Unregister-stale-platform-devices/20190902-001307
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.4.0-11) 7.4.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/acpi/acpi_platform.c: In function 'acpi_platform_device_find_by_adev':
>> drivers/acpi/acpi_platform.c:38:8: error: implicit declaration of function 'bus_find_device_by_acpi_dev'; did you mean 'bus_find_device_by_name'? [-Werror=implicit-function-declaration]
     dev = bus_find_device_by_acpi_dev(&platform_bus_type, adev);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~
           bus_find_device_by_name
   drivers/acpi/acpi_platform.c:38:6: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
     dev = bus_find_device_by_acpi_dev(&platform_bus_type, adev);
         ^
   cc1: some warnings being treated as errors

vim +38 drivers/acpi/acpi_platform.c

    33	
    34	static struct platform_device *acpi_platform_device_find_by_adev(struct acpi_device *adev)
    35	{
    36		struct device *dev;
    37	
  > 38		dev = bus_find_device_by_acpi_dev(&platform_bus_type, adev);
    39		return dev ? to_platform_device(dev) : NULL;
    40	}
    41	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 43497 bytes --]

  parent reply	other threads:[~2019-09-02  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 14:34 [PATCH v1] ACPI / platform: Unregister stale platform devices Andy Shevchenko
2019-09-02  6:38 ` kbuild test robot
2019-09-02  9:52   ` Andy Shevchenko
2019-09-04  8:46     ` [kbuild-all] " Rong Chen
2019-09-02  7:19 ` kbuild test robot [this message]
2019-09-02  9:55   ` Andy Shevchenko
2019-10-17 11:38 ` Andy Shevchenko
2019-10-17 21:57 ` Rafael J. Wysocki
2019-10-18  8:35   ` Andy Shevchenko

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=201909021519.YR3Jdy5T%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=fntoth@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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