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 S1752697AbcAGDva (ORCPT <rfc822;w@1wt.eu>);
	Wed, 6 Jan 2016 22:51:30 -0500
Received: from mga01.intel.com ([192.55.52.88]:52665 "EHLO mga01.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750892AbcAGDv2 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 6 Jan 2016 22:51:28 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,531,1444719600"; 
   d="scan'208";a="887895614"
Message-ID: <568DE0BE.9030108@linux.intel.com>
Date: Thu, 07 Jan 2016 11:51:26 +0800
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Steven Rostedt <rostedt@goodmis.org>
CC: "Qiu, PeiyangX" <peiyangx.qiu@intel.com>, linux-kernel@vger.kernel.org,
        Rusty Russell <rusty@rustcorp.com.au>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] trace: correct start_index in find_next
References: <5684B900.9000309@intel.com>	<568DD3F8.9050903@linux.intel.com> <20160106225016.2e730dd3@gandalf.local.home>
In-Reply-To: <20160106225016.2e730dd3@gandalf.local.home>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 2016/1/7 11:50, Steven Rostedt wrote:
> On Thu, 07 Jan 2016 10:56:56 +0800
> "Zhang, Yanmin" <yanmin_zhang@linux.intel.com> wrote:
>
>> How is this patch? It fixes a kernel panic.
>>
> Linus already pulled it. It's also marked for stable. See commit:
> f36d1be2930ede0a1947686e1126ffda5d5ee1bb in Linus's tree.
>
> I renamed the subject slightly to:
>
> "tracing: Fix setting of start_index in find_next()"
>
Thanks as usual.