From: Hongyan Xia <hongyan.xia@transsion.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: 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>,
Jiazi Li <jiazi.li@transsion.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] sched: Move some scheduler fields to new static branch API
Date: Wed, 19 Aug 2026 10:02:10 +0000 [thread overview]
Message-ID: <38a15c3c-9e95-4b24-abc2-44956e65cea6@transsion.com> (raw)
In-Reply-To: <20260819092803.GH1247881@noisy.programming.kicks-ass.net>
On 8/19/2026 5:28 PM, Peter Zijlstra wrote:
> On Wed, Aug 19, 2026 at 09:04:03AM +0000, Hongyan Xia wrote:
>> On 8/19/2026 4:44 PM, Peter Zijlstra wrote:
>>> On Wed, Aug 19, 2026 at 08:09:38AM +0000, Hongyan Xia wrote:
>>>> From: Hongyan Xia <hongyan.xia@transsion.com>
>>>>
>>>> __cfs_bandwidth_used uses struct static_key directly which is
>>>> deprecated. Fix.
>>>>
>>>> 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.
>>>>
>>>> No functional change.
>>>>
>>>> Signed-off-by: Hongyan Xia <hongyan.xia@transsion.com>
>>>> ---
>>>
>>> Your emails are encoded in a Microsoft special quoted-printable that my
>>> scripts don't like.
>>
>> Hmm, this patch was sent through the normal git format-patch and
>> send-email flow, which looks okay on my end and via lore. Do you have
>> more details so that I can debug and avoid triggering future unhappiness
>> in your scripts?
>
> I think I fixed the script. But what the thing did was encode '\n' as
> =0A=. This is two tokens: "=0A" for the '\n' and then "=$" for a
> continuation line.
>
> It does this for every line, including the last line. Marking the last
> line as having a continuation resulted in no output, it would just eat
> the whole message.
>
> Marking the last line as having a continuation is well, bonkers. But my
> script should now be able to deal with it. Still, pretty idiotic
> behaviour on whoever mangled that.
I see it now. I sent this patch again to myself and downloaded the mbox.
No such weird tokens in the original patch but they appear in the mbox I
received.
A quick search suggests this is a known issue, done during email transit
by Microsoft. This is too dumb to be true and I am shocked. Thanks a
million for fixing it on your end.
next prev parent reply other threads:[~2026-08-19 10:02 UTC|newest]
Thread overview: 10+ 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 [this message]
2026-09-02 8:18 ` Hongyan Xia
2026-09-02 8:19 ` Peter Zijlstra
2026-08-19 12:19 ` Shrikanth Hegde
2026-08-19 12:58 ` Peter Zijlstra
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=38a15c3c-9e95-4b24-abc2-44956e65cea6@transsion.com \
--to=hongyan.xia@transsion.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jiazi.li@transsion.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.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®