From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [Question] sched: rt.c: kernel-doc warning
Date: Mon, 12 Oct 2026 15:15:56 +0530 [thread overview]
Message-ID: <0c57bf52-2c28-4379-9c1b-4f35a8540c3b@amd.com> (raw)
In-Reply-To: <20261005072738.2902503-2-manuelebnerli@mailbox.org>
Hello Manuel,
On 10/5/2026 12:57 PM, Manuel Ebner wrote:
> [You don't often get email from manuelebnerli@mailbox.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi,
>
> I'm trying to fix built warning and stumbled over this one:
>
> $make W=1 -j8 > make_output.txt
> In file included from kernel/sched/build_policy.c:52:
> kernel/sched/rt.c:12:18: warning: ‘max_rt_runtime’ defined but not used [-Wunused-const-variable=]
> 12 | static const u64 max_rt_runtime = MAX_BW;
> | ^~~~~~~~~~~~~~
>
> I just can't make sense of this, because max_rt_runtime is used later in the
> file - see diff.
> What am I missing?
Any chance you have both CONFIG_RT_GROUP_SCHED and CONFIG_SYSCTL
disabled in your .config?
In that case, max_rt_runtime is never used by anything that gets
built in and the compiler complains. You can annotate it with
__maybe_unused to keep the build happy in those cases.
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2026-10-12 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 7:27 Manuel Ebner
2026-10-12 9:45 ` K Prateek Nayak [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=0c57bf52-2c28-4379-9c1b-4f35a8540c3b@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®