From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2019.03.12a 64/65] kernel//rcu/rcuperf.c:198:1: error: expected ';' before '}' token
Date: Mon, 18 Mar 2019 15:37:52 -0700 [thread overview]
Message-ID: <20190318223752.GQ4102@linux.ibm.com> (raw)
In-Reply-To: <201903190610.Qjc7Zt6J%lkp@intel.com>
On Tue, Mar 19, 2019 at 06:06:12AM +0800, kbuild test robot wrote:
> 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
Looks like I need to break out the brown paper bag! :-/
I have a fixup patch on my v5.1-rc1 branch.
Thanx, Paul
prev parent reply other threads:[~2019-03-18 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 22:06 [rcu:dev.2019.03.12a 64/65] kernel//rcu/rcuperf.c:198:1: error: expected ';' before '}' token kbuild test robot
2019-03-18 22:37 ` Paul E. McKenney [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=20190318223752.GQ4102@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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.