linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:misc.compat 1/2] arch/alpha/kernel/pci.c:412:35: error: expected ')' before 'long'
Date: Wed, 28 Mar 2018 15:38:14 +0800	[thread overview]
Message-ID: <201803281511.VYh8rVfg%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git misc.compat
head:   1698ba656f7d075f9202812ee41ac0b70381f2b9
commit: f5eaa2a790b08155411fd49ef21ebf059a345445 [1/2] alpha: switch pci syscalls to SYSCALL_DEFINE
config: alpha-defconfig (attached as .config)
compiler: alpha-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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 f5eaa2a790b08155411fd49ef21ebf059a345445
        # save the attached .config to linux build tree
        make.cross ARCH=alpha 

All errors (new ones prefixed by >>):

>> arch/alpha/kernel/pci.c:412:35: error: expected ')' before 'long'
    SYSCALL_DEFINE3(pciconfig_iobase, long, which, unsigned long, bus,
                                      ^~~~

vim +412 arch/alpha/kernel/pci.c

   407	
   408	
   409	/* Provide information on locations of various I/O regions in physical
   410	   memory.  Do this on a per-card basis so that we choose the right hose.  */
   411	
 > 412	SYSCALL_DEFINE3(pciconfig_iobase, long, which, unsigned long, bus,
   413			unsigned long, dfn)
   414	{
   415		struct pci_controller *hose;
   416		struct pci_dev *dev;
   417	
   418		/* from hose or from bus.devfn */
   419		if (which & IOBASE_FROM_HOSE) {
   420			for(hose = hose_head; hose; hose = hose->next) 
   421				if (hose->index == bus) break;
   422			if (!hose) return -ENODEV;
   423		} else {
   424			/* Special hook for ISA access.  */
   425			if (bus == 0 && dfn == 0) {
   426				hose = pci_isa_hose;
   427			} else {
   428				dev = pci_get_domain_bus_and_slot(0, bus, dfn);
   429				if (!dev)
   430					return -ENODEV;
   431				hose = dev->sysdata;
   432				pci_dev_put(dev);
   433			}
   434		}
   435	
   436		switch (which & ~IOBASE_FROM_HOSE) {
   437		case IOBASE_HOSE:
   438			return hose->index;
   439		case IOBASE_SPARSE_MEM:
   440			return hose->sparse_mem_base;
   441		case IOBASE_DENSE_MEM:
   442			return hose->dense_mem_base;
   443		case IOBASE_SPARSE_IO:
   444			return hose->sparse_io_base;
   445		case IOBASE_DENSE_IO:
   446			return hose->dense_io_base;
   447		case IOBASE_ROOT_BUS:
   448			return hose->bus->number;
   449		}
   450	
   451		return -EOPNOTSUPP;
   452	}
   453	

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

                 reply	other threads:[~2018-03-28  7:38 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=201803281511.VYh8rVfg%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).