linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: kbuild-all@lists.01.org, linux-pci@vger.kernel.org
Subject: [pci:pci/pm-2 13/15] drivers/xen/platform-pci.c:172:20: error: initialization from incompatible pointer type
Date: Sat, 2 Nov 2019 12:29:17 +0800	[thread overview]
Message-ID: <201911021204.E9NUpEXD%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/pm-2
head:   c0f8be2112be6e3b6fd6f57aae094c8c9ebdbf7f
commit: b919d7498411559be7d9f8c2de0b7fe24ae32208 [13/15] xen-platform: Convert to generic power management
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
        git checkout b919d7498411559be7d9f8c2de0b7fe24ae32208
        # 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/xen/platform-pci.c:172:20: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
     .resume_noirq =   platform_pci_resume,
                       ^~~~~~~~~~~~~~~~~~~
   drivers/xen/platform-pci.c:172:20: note: (near initialization for 'platform_pm_ops.resume_noirq')
   cc1: some warnings being treated as errors

vim +172 drivers/xen/platform-pci.c

   170	
   171	static struct dev_pm_ops platform_pm_ops = {
 > 172		.resume_noirq =   platform_pci_resume,
   173	};
   174	

---
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: 70867 bytes --]

                 reply	other threads:[~2019-11-02  4:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201911021204.E9NUpEXD%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=helgaas@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-pci@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).