linux-kernel - Re: [PATCH v6.12 0/4] sched: The newidle balance regression

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2026010851-achiness-clustered-2cac@gregkh>
Date: Thu, 8 Jan 2026 11:10:58 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Ajay Kaher <ajay.kaher@...adcom.com>
Cc: stable@...r.kernel.org, mingo@...hat.com, peterz@...radead.org,
	juri.lelli@...hat.com, vincent.guittot@...aro.org,
	dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
	mgorman@...e.de, vschneid@...hat.com, linux-kernel@...r.kernel.org,
	alexey.makhalov@...adcom.com, yin.ding@...adcom.com,
	tapas.kundu@...adcom.com
Subject: Re: [PATCH v6.12 0/4] sched: The newidle balance regression

On Thu, Dec 04, 2025 at 10:36:02AM +0530, Ajay Kaher wrote:
> On Wed, Dec 3, 2025 at 6:46 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> >
> > On Wed, Dec 03, 2025 at 05:23:05PM +0530, Ajay Kaher wrote:
> > > Greg, following upstream patches will directly apply to v6.17, so I am
> > > not sending for v6.17:
> > >
> > > https://github.com/torvalds/linux/commit/d206fbad9328ddb68ebabd7cf7413392acd38081.patch
> > > https://github.com/torvalds/linux/commit/e78e70dbf603c1425f15f32b455ca148c932f6c1.patch
> > > https://github.com/torvalds/linux/commit/08d473dd8718e4a4d698b1113a14a40ad64a909b.patch
> > > https://github.com/torvalds/linux/commit/33cf66d88306663d16e4759e9d24766b0aaa2e17.patch
> >
> > Please don't use github for kernel stuff....
> 
> ok.
> 
> > Anyway, these are not in a -rc kernel yet, so I really shouldn't be
> > taking them unless the author/maintainer agrees they should go in
> > "right now".  And given that these weren't even marked as cc: stable in
> > the first place, why the rush?
> 
> Agree. No rush.
> 
> > Also, you forgot about 6.18.y, right?
> 
> Yes. However, upstream patches will directly apply till v6.17.

Sorry for the delay, now queued up.

greg k-h