From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751455AbdGROBG (ORCPT <rfc822;w@1wt.eu>);
        Tue, 18 Jul 2017 10:01:06 -0400
Received: from mga11.intel.com ([192.55.52.93]:36406 "EHLO mga11.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751408AbdGROBF (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 18 Jul 2017 10:01:05 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.40,378,1496127600"; 
   d="scan'208";a="1196809699"
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Alexey Budankov <alexey.budankov@linux.intel.com>,
        Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
        Dmitri Prokhorov <Dmitry.Prohorov@intel.com>,
        Valery Cherepennikov <valery.cherepennikov@intel.com>,
        Mark Rutland <mark.rutland@arm.com>,
        David Carrillo-Cisneros <davidcc@google.com>,
        Stephane Eranian <eranian@google.com>,
        linux-kernel <linux-kernel@vger.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
In-Reply-To: <b5f616ad-1dd9-c66a-96f0-75b9489ae099@linux.intel.com>
References: <bbd389bd-4d8b-d677-bded-850d8296596b@linux.intel.com> <33f0e89c-9252-c154-cd11-5f4dd06bdb3a@linux.intel.com> <87h8yavv20.fsf@ashishki-desk.ger.corp.intel.com> <b5f616ad-1dd9-c66a-96f0-75b9489ae099@linux.intel.com>
User-Agent: Notmuch/0.23.7 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Tue, 18 Jul 2017 17:01:01 +0300
Message-ID: <87vampvo82.fsf@ashishki-desk.ger.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Alexey Budankov <alexey.budankov@linux.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.

> 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