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: Tue, 18 Jul 2017 17:30:37 +0300 From: Alexey Budankov <alexey.budankov@...ux.intel.com> To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org> Cc: Andi Kleen <ak@...ux.intel.com>, Kan Liang <kan.liang@...el.com>, Dmitri Prokhorov <Dmitry.Prohorov@...el.com>, Valery Cherepennikov <valery.cherepennikov@...el.com>, Mark Rutland <mark.rutland@....com>, David Carrillo-Cisneros <davidcc@...gle.com>, Stephane Eranian <eranian@...gle.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v5 4/4]: perf/core: complete replace of lists by rb trees for pinned and flexible groups at perf_event_context Hi, On 18.07.2017 17:01, Alexander Shishkin wrote: > Alexey Budankov <alexey.budankov@...ux.intel.com> writes: > >>> Apparently the patches are not threaded, so one needs to fish them out >>> one by one in order to review. >> >> Thanks for feedback. The BKM in this case is just to keep subject unchanged, right? > > No, just use git-send-email, it will set all the email headers correctly > (In-Reply-To, References etc). The subject line is a short description > of the patch, so must be different for each patch. Ok. I see. So what are the next steps needs to be taken towards the upstream of this work? What do I need to do more to have this stuff included into the kernel? Could you please clarify this? > >> Just mentioned branch and revision when forking local development branch. >> Considered it helpful for applying the whole patch set. > > You may want to mention this if you're basing your patchset off of some > older kernel or if it depends on another patchset that's not merged yet, > but tip/perf/core (I think) is the default assumption. > > Regards, > -- > Alex > Thanks, Alexey
Powered by blists - more mailing lists