mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2019.03.12a 64/65] kernel//rcu/rcuperf.c:198:1: error: expected ';' before '}' token
Date: Tue, 19 Mar 2019 06:06:12 +0800	[thread overview]
Message-ID: <201903190610.Qjc7Zt6J%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.03.12a
head:   667a45dd2b898f2aaf6dcbfa471c8a23f603bde5
commit: a3f5f4fae7255e7ed4a5a8be80612cdd76c65ac6 [64/65] rcu: Forbid DEFINE{,_STATIC}_SRCU() from modules
config: i386-randconfig-x077-201911 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout a3f5f4fae7255e7ed4a5a8be80612cdd76c65ac6
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   kernel//rcu/rcuperf.c: In function 'srcu_sync_perf_init':
>> kernel//rcu/rcuperf.c:198:1: error: expected ';' before '}' token
    }
    ^

vim +198 kernel//rcu/rcuperf.c

   194	
   195	static void srcu_sync_perf_init(void)
   196	{
   197		srcu_ctlp = &srcu_ctl_perf
 > 198	}
   199	#endif
   200	

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

             reply	other threads:[~2019-03-18 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 22:06 kbuild test robot [this message]
2019-03-18 22:37 ` Paul E. McKenney

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=201903190610.Qjc7Zt6J%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®