From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D325142C4E8 for ; Wed, 19 Aug 2026 09:28:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787131699; cv=none; b=E1Inl+VzhcqCNf0g1uAIFfiEPxHLbQNMSGgGh0XyBI+hH5gmT/Dt423/xpXG8vjGtvlycc+HOVqqvrFHhvrtWtgGADztBIToawHdymWuln6EO90I4UJ5TbhBlUkfvBIjmnRbjLQBCVheESP1qu7RngQdpJhyynOXAdWWR/LTOyg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787131699; c=relaxed/simple; bh=73nIqmg+vPGWTFaSJVI5rshVB83HtItH5Sa+xHLk4+4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GfVx/rcp//mKw/XvETAVrh7Nvni/0BwP2eZQ2BoYPJ/CoY1otm7u/qt5JVQ2CUxQO4nSEr21chZPgIuULGflk1LQHwGjYzbDGMMmNkxZlFY/lnslwRqx16zK5Az6wWYDhpta3zl5uaZ7/Rqp3At5YiRqdsdGFKtjzAo+ceVsIwU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=pass smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=MXhi54G3; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="MXhi54G3" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=M73OeCqEc1C9K/+DBcB1Kw9nR2pVOHJNjdoT3yUIfjQ=; b=MXhi54G3XP95nr3jsi151k90iV L6NbQLHJhEhpvyRJgHKv1zpe4rwunQkUvUhNFo2Xy6Lj6VEG3otD0f95/3ZH5HptKJECC7sUQw3UI FUnbWopdG8ac/fpVFpRlIpoMoohGu0KdF1Ph/G97BcB0qsPabyQqShose5uJESrtEMnrcJBfoI+iv AQdeZBey5cvunD1Mo8Y/awgCtKu18lzkbov7XuuO7vWIyHqKrS4V/z4Re911v8tWf/9UgTLvtpnL5 WViF1/ETsmduRLPncG1TXjEOm18hdIS+BB8zhHt68tmGImgWYDM0I2RH9WY0uXDrwWBVWPwN7J2GR MpBiI2xA==; Received: from 77-249-17-252.cable.dynamic.v4.ziggo.nl ([77.249.17.252] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.99.1 #2 (Red Hat Linux)) id 1wwcaa-0000000DQUh-0vrA; Wed, 19 Aug 2026 09:28:04 +0000 Received: by noisy.programming.kicks-ass.net (Postfix, from userid 1000) id 2F62130030F; Wed, 19 Aug 2026 11:28:03 +0200 (CEST) Date: Wed, 19 Aug 2026 11:28:03 +0200 From: Peter Zijlstra To: Hongyan Xia Cc: Ingo Molnar , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Valentin Schneider , K Prateek Nayak , Jiazi Li , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH RESEND] sched: Move some scheduler fields to new static branch API Message-ID: <20260819092803.GH1247881@noisy.programming.kicks-ass.net> References: <20260819080932.11564-1-hongyan.xia@transsion.com> <20260819084438.GG1247881@noisy.programming.kicks-ass.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 > >> > >> __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 > >> --- > > > > 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.