public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: Alexandru Gagniuc <mr.nuke.me@gmail.com>,
	kbuild-all@01.org, linux-pci@vger.kernel.org
Subject: Re: [pci:pci/hotplug 4/5] include/linux/pci_hotplug.h:145:1: error: expected identifier or '(' before '{' token
Date: Mon, 22 Apr 2019 18:03:55 -0500	[thread overview]
Message-ID: <20190422230355.GN173520@google.com> (raw)
In-Reply-To: <201904230541.l1Tz6i3p%lkp@intel.com>

On Tue, Apr 23, 2019 at 05:19:48AM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/hotplug
> head:   d98ba96a72ca1a1dd9d2f3a321e64bac3d94bd39
> commit: 93395b9ebeb0cfee5e5c617ec44d249d19439126 [4/5] PCI / ACPI: Remove the need for 'struct hotplug_params'
> config: xtensa-common_defconfig (attached as .config)
> compiler: xtensa-linux-gcc (GCC) 8.1.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 93395b9ebeb0cfee5e5c617ec44d249d19439126
>         # save the attached .config to linux build tree
>         GCC_VERSION=8.1.0 make.cross ARCH=xtensa 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> 
> All errors (new ones prefixed by >>):
> 
>    In file included from drivers/pci/pci.c:30:
> >> include/linux/pci_hotplug.h:145:1: error: expected identifier or '(' before '{' token
>     {
>     ^

I fixed this and updated the pci/hotplug branch.

Bjorn

      reply	other threads:[~2019-04-22 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 21:19 [pci:pci/hotplug 4/5] include/linux/pci_hotplug.h:145:1: error: expected identifier or '(' before '{' token kbuild test robot
2019-04-22 23:03 ` Bjorn Helgaas [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=20190422230355.GN173520@google.com \
    --to=helgaas@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mr.nuke.me@gmail.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