linux-kernel - Re: [GIT PULL] sched_ext: Initial pull request for v6.11

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: <ZrKFpCz2hbSjvE5M@slm.duckdns.org>
Date: Tue, 6 Aug 2024 10:20:52 -1000
From: Tejun Heo <tj@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, David Vernet <void@...ifault.com>,
	Ingo Molnar <mingo@...hat.com>, Alexei Starovoitov <ast@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL] sched_ext: Initial pull request for v6.11

Hello, Peter.

On Tue, Aug 06, 2024 at 10:18:45PM +0200, Peter Zijlstra wrote:
...
> OK. So my plan was to finish reading the for 6.11 pull diff, and then
> merge that eevdf patch-set I send out. Post those patches I had in
> sched/prep that re-arrange the put_prev thing. Then merge those, and
> then ask you to rebase the whole lot on top of that, after which I'll
> pull your branch.

Oh... I'm planning to keep the tree history and just send the pull request
to Linus. I can just follow the core changes and update accordingly as
necessary.

Thanks.

-- 
tejun