From: "Paul E. McKenney" <paulmck@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
rcu@vger.kernel.org, open list <linux-kernel@vger.kernel.org>,
josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
Joel Fernandes <joel@joelfernandes.org>,
lkft-triage@lists.linaro.org
Subject: Re: kernel/rcu/tasks.h:1070:37: error: ‘rcu_tasks_rude’ undeclared
Date: Wed, 18 Mar 2020 09:05:12 -0700 [thread overview]
Message-ID: <20200318160512.GT3199@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CA+G9fYsT2B0WFPV0uohH=QT+CU09OscZvsUV3pnhG-xjPF+OqA@mail.gmail.com>
On Wed, Mar 18, 2020 at 09:26:01PM +0530, Naresh Kamboju wrote:
> The arm64 build failed on linux-next master branch.
>
> make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=gcc CC="sccache
> aarch64-linux-gnu-gcc" O=build Image
>
> In file included from ../kernel/rcu/update.c:562:
> ../kernel/rcu/tasks.h: In function ‘show_rcu_tasks_gp_kthreads’:
> ../kernel/rcu/tasks.h:1070:37: error: ‘rcu_tasks_rude’ undeclared
> (first use in this function); did you mean ‘rcu_tasks_qs’?
> 1070 | show_rcu_tasks_generic_gp_kthread(&rcu_tasks_rude, "");
> | ^~~~~~~~~~~~~~
> | rcu_tasks_qs
> ../kernel/rcu/tasks.h:1070:37: note: each undeclared identifier is
> reported only once for each function it appears in
>
> Ref:
> https://gitlab.com/Linaro/lkft/kernel-runs/-/jobs/476084417
Good catch, but kbuild test robot beat you to it. A fix is on its
way, and thank you for your testing efforts!
Thanx, Paul
prev parent reply other threads:[~2020-03-18 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 15:56 kernel/rcu/tasks.h:1070:37: error: ‘rcu_tasks_rude’ undeclared Naresh Kamboju
2020-03-18 16:05 ` 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=20200318160512.GT3199@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=naresh.kamboju@linaro.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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).