From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rostedt@goodmis.org>
Date: Tue, 26 Jul 2016 23:12:42 -0400
From: Steven Rostedt <rostedt@goodmis.org>
To: Vinod Koul <vinod.koul@intel.com>
Message-ID: <20160726231242.7c993900@grimm.local.home>
In-Reply-To: <20160711141833.GK9681@localhost>
References: <alpine.LNX.2.00.1607082339040.24757@cbobk.fhfr.pm>
	<20160709000631.GB8989@io.lakedaemon.net>
	<1468024946.2390.21.camel@HansenPartnership.com>
	<alpine.LNX.2.00.1607091039550.24757@cbobk.fhfr.pm>
	<20160709093626.GA6247@sirena.org.uk>
	<20160710162203.GA9681@localhost>
	<20160710170117.GI26097@thunk.org>
	<20160711050000.GC9681@localhost>
	<20160711051335.GQ26097@thunk.org>
	<20160711141833.GK9681@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	ksummit-discuss@lists.linux-foundation.org,
	Jason Cooper <jason@lakedaemon.net>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] stable workflow
List-Id: <ksummit-discuss.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/ksummit-discuss/>
List-Post: <mailto:ksummit-discuss@lists.linuxfoundation.org>
List-Help: <mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=subscribe>

On Mon, 11 Jul 2016 19:48:34 +0530
Vinod Koul <vinod.koul@intel.com> wrote:

> But the person might be slightly better off than you or me :-)
> 

I still believe that it comes down to the maintainer making the final
decision about marking a patch as stable. If they don't have the
hardware to test it, then they should then ask the patch submitter to
test for stable. If the submitter doesn't want to for whatever reason,
then that patch simply shouldn't be marked for stable.

-- Steve