From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from foss.arm.com ([217.140.101.70]:36944 "EHLO foss.arm.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S934085AbcCOOgo (ORCPT <rfc822;stable@vger.kernel.org>);
	Tue, 15 Mar 2016 10:36:44 -0400
Date: Tue, 15 Mar 2016 14:39:06 +0000
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: gregkh@linuxfoundation.org, catalin.marinas@arm.com,
	takahiro.akashi@linaro.org, will.deacon@arm.com,
	stable@vger.kernel.org, stable-commits@vger.kernel.org,
	sudeep.holla@arm.com
Subject: Re: Patch "arm64: kernel: pause/unpause function graph tracer in
 cpu_suspend()" has been added to the 4.1-stable tree
Message-ID: <20160315143906.GA14633@red-moon>
References: <1453877690189116@kroah.com>
 <20160315140806.GA11376@red-moon>
 <20160315100753.7f97bf4c@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160315100753.7f97bf4c@gandalf.local.home>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Tue, Mar 15, 2016 at 10:07:53AM -0400, Steven Rostedt wrote:
> On Tue, 15 Mar 2016 14:08:19 +0000
> Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> 
> > Hi Greg,
> > 
> > On Tue, Jan 26, 2016 at 10:54:50PM -0800, gregkh@linuxfoundation.org wrote:
> > > 
> > > This is a note to let you know that I've just added the patch titled
> > > 
> > >     arm64: kernel: pause/unpause function graph tracer in cpu_suspend()
> > > 
> > > to the 4.1-stable tree which can be found at:
> > >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > > 
> > > The filename of the patch is:
> > >      arm64-kernel-pause-unpause-function-graph-tracer-in-cpu_suspend.patch
> > > and it can be found in the queue-4.1 subdirectory.
> > > 
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.  
> > 
> > We have just noticed this patch did not make it to 3.18 stable kernel
> > even though it was marked for #3.16+, probably it has slipped through
> > the cracks, please let us know what we can do to get it applied
> > to the 3.18 stable tree.
> > 
> 
> Does it apply without conflicts or break the build?

I checked when I marked it for stable 3.16+ but to make sure everything
is fine I have just rechecked against 3.18.28, it applies cleanly and does
not break the build so I hope it can be considered for inclusion.

Thanks,
Lorenzo