From: Peter Zijlstra <peterz@infradead.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: Hongyan Xia <hongyan.xia@transsion.com>,
Jiazi Li <jiazi.li@transsion.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
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>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH RESEND] sched: Move some scheduler fields to new static branch API
Date: Wed, 19 Aug 2026 14:58:08 +0200 [thread overview]
Message-ID: <20260819125808.GR776954@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <ad4a34fa-e923-4725-a42d-ffea6423d2f5@linux.ibm.com>
On Wed, Aug 19, 2026 at 05:49:48PM +0530, Shrikanth Hegde wrote:
> Hi Hongyan.
>
> On 8/19/26 1:39 PM, Hongyan Xia wrote:
> > From: Hongyan Xia <hongyan.xia@transsion.com>
> >
> > __cfs_bandwidth_used uses struct static_key directly which is
> > deprecated. Fix.
>
> A bit of context on why it is deprecated would help.
>
> >
> > sk_dynamic_* uses static_key_{enable/disable}(), which aren't really
> > deprecated, but take the opportunity to move to the new static_branch_*
> > APIs to be consistent.
> >
>
> Mark had a series to remove a few of them completely. IIRC only lazy
> check will remain.
Yeah, I have those pending. I'll smash everything together and see where
the pieces fall post -rc1.
next prev parent reply other threads:[~2026-08-19 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:09 Hongyan Xia
2026-08-19 8:44 ` Peter Zijlstra
2026-08-19 9:04 ` Hongyan Xia
2026-08-19 9:28 ` Peter Zijlstra
2026-08-19 10:02 ` Hongyan Xia
2026-08-19 12:19 ` Shrikanth Hegde
2026-08-19 12:58 ` Peter Zijlstra [this message]
2026-08-20 2:21 ` Hongyan Xia
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=20260819125808.GR776954@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hongyan.xia@transsion.com \
--cc=jiazi.li@transsion.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--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®