All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:rcu/dev 111/113] drivers//iommu/amd_iommu.c:3566:22: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'stupid_workaround'
Date: Thu, 7 Jun 2018 17:49:19 +0800	[thread overview]
Message-ID: <201806071704.nfKIWO14%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev
head:   e4cd9c98498575e44585e74bf2cf1b45bc42a697
commit: 7d9ca00a259aa549acd99ba91d634c62430a94ea [111/113] EXP iommu: Placeholder for fix in mainline
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        git checkout 7d9ca00a259aa549acd99ba91d634c62430a94ea
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers//iommu/amd_iommu.c:3566:22: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'stupid_workaround'
    void __maxybe_unused stupid_workaround(void)
                         ^~~~~~~~~~~~~~~~~

vim +3566 drivers//iommu/amd_iommu.c

  3565	
> 3566	void __maxybe_unused stupid_workaround(void)
  3567	{
  3568		spin_lock(&iommu_table_lock);
  3569		spin_unlock(&iommu_table_lock);
  3570	}
  3571	

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

                 reply	other threads:[~2018-06-07  9:50 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=201806071704.nfKIWO14%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.