From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752081AbdGROao (ORCPT ); Tue, 18 Jul 2017 10:30:44 -0400 Received: from mga01.intel.com ([192.55.52.88]:53595 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751778AbdGROan (ORCPT ); Tue, 18 Jul 2017 10:30:43 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,378,1496127600"; d="scan'208";a="994316572" Subject: Re: [PATCH v5 4/4]: perf/core: complete replace of lists by rb trees for pinned and flexible groups at perf_event_context To: Alexander Shishkin , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo Cc: Andi Kleen , Kan Liang , Dmitri Prokhorov , Valery Cherepennikov , Mark Rutland , David Carrillo-Cisneros , Stephane Eranian , linux-kernel References: <33f0e89c-9252-c154-cd11-5f4dd06bdb3a@linux.intel.com> <87h8yavv20.fsf@ashishki-desk.ger.corp.intel.com> <87vampvo82.fsf@ashishki-desk.ger.corp.intel.com> From: Alexey Budankov Organization: Intel Corp. Message-ID: <43f69bfc-25b4-9bee-5b25-90d73ec61041@linux.intel.com> Date: Tue, 18 Jul 2017 17:30:37 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <87vampvo82.fsf@ashishki-desk.ger.corp.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 18.07.2017 17:01, Alexander Shishkin wrote: > Alexey Budankov 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