linux-kernel - Re: Re: [PATCH] sched/fair: Correct CPU selection from isolated domain

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <tencent_02C238CCB4CAA1D0C58AF9A89E8263AE740A@qq.com>
Date: Tue, 30 Jul 2024 17:40:17 +0800
From: wujing <realwujing@...com>
To: gregkh@...uxfoundation.org
Cc: dongml2@...natelecom.cn,
	linux-kernel@...r.kernel.org,
	menglong8.dong@...il.com,
	mingo@...hat.com,
	peterz@...radead.org,
	realwujing@...com,
	stable@...r.kernel.org,
	yuanql9@...natelecom.cn
Subject: Re: Re: [PATCH] sched/fair: Correct CPU selection from isolated domain

> What "current patch"?
>
> confused,
>
> greg k-h

The current patch is in my first email. Please ignore the previous two emails.
The "current patch" mentioned in the earlier emails refers to the upstream
status, but the latest upstream patch can no longer be applied to linux-4.19.y.