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
| ||
|
Date: Wed, 25 Nov 2020 09:41:12 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Joel Fernandes <joel@...lfernandes.org> Cc: Nishanth Aravamudan <naravamudan@...italocean.com>, Julien Desfossez <jdesfossez@...italocean.com>, Tim Chen <tim.c.chen@...ux.intel.com>, Vineeth Pillai <viremana@...ux.microsoft.com>, Aaron Lu <aaron.lwe@...il.com>, Aubrey Li <aubrey.intel@...il.com>, tglx@...utronix.de, linux-kernel@...r.kernel.org, mingo@...nel.org, torvalds@...ux-foundation.org, fweisbec@...il.com, keescook@...omium.org, kerrnel@...gle.com, Phil Auld <pauld@...hat.com>, Valentin Schneider <valentin.schneider@....com>, Mel Gorman <mgorman@...hsingularity.net>, Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, Paolo Bonzini <pbonzini@...hat.com>, vineeth@...byteword.org, Chen Yu <yu.c.chen@...el.com>, Christian Brauner <christian.brauner@...ntu.com>, Agata Gruza <agata.gruza@...el.com>, Antonio Gomez Iglesias <antonio.gomez.iglesias@...el.com>, graf@...zon.com, konrad.wilk@...cle.com, dfaggioli@...e.com, pjt@...gle.com, rostedt@...dmis.org, derkling@...gle.com, benbjiang@...cent.com, Alexandre Chartre <alexandre.chartre@...cle.com>, James.Bottomley@...senpartnership.com, OWeisse@...ch.edu, Dhaval Giani <dhaval.giani@...cle.com>, Junaid Shahid <junaids@...gle.com>, jsbarnes@...gle.com, chris.hyser@...cle.com, Ben Segall <bsegall@...gle.com>, Josh Don <joshdon@...gle.com>, Hao Luo <haoluo@...gle.com>, Tom Lendacky <thomas.lendacky@....com>, Aubrey Li <aubrey.li@...ux.intel.com>, "Paul E. McKenney" <paulmck@...nel.org>, Tim Chen <tim.c.chen@...el.com> Subject: Re: [PATCH -tip 15/32] sched: Improve snapshotting of min_vruntime for CGroups On Tue, Nov 24, 2020 at 12:07:44PM -0500, Joel Fernandes wrote: > Either way would be Ok with me, I would suggest retaining the history though > so that the details in the changelog are preserved of the issues we faced, > and in the future we can refer back to them. Well, in part that's what we have mail archives for. My main concern is that there's a lot of back and forth in the patches as presented and that makes review really awkward. I've done some of the patch munging proposed, I might do more if I find the motivation. But first I should probably go read all that API crud you did on top, I've not read that before...
Powered by blists - more mailing lists