From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1425872AbdEZIwb (ORCPT ); Fri, 26 May 2017 04:52:31 -0400 Received: from verein.lst.de ([213.95.11.211]:41814 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1425858AbdEZIw1 (ORCPT ); Fri, 26 May 2017 04:52:27 -0400 Date: Fri, 26 May 2017 10:52:25 +0200 From: Christoph Hellwig To: Andy Lutomirski Cc: Jens Axboe , Christoph Hellwig , Sagi Grimberg , Keith Busch , "linux-kernel@vger.kernel.org" , Kai-Heng Feng , linux-nvme Subject: Re: [PATCH 1/2] nvme: Wait at least 6000ms before entering the deepest idle state Message-ID: <20170526085225.GA28728@lst.de> References: <6760ae9459ba19657f8009a9231b97a71114a1e5.1495663545.git.luto@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6760ae9459ba19657f8009a9231b97a71114a1e5.1495663545.git.luto@kernel.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 24, 2017 at 03:06:30PM -0700, Andy Lutomirski wrote: > This should at least make vendors less nervous about Linux's APST > policy. I'm not aware of any concrete bugs it would fix (although I > was hoping it would fix the Samsung/Dell quirk). > > Cc: stable@vger.kernel.org # v4.11 Just following a somewhat odd and arbitray policy from another driver that doesn't fix anything by itself certainly isn't stable material. And to be honest I'm not sure what applying it will gain us at all. From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Fri, 26 May 2017 10:52:25 +0200 Subject: [PATCH 1/2] nvme: Wait at least 6000ms before entering the deepest idle state In-Reply-To: <6760ae9459ba19657f8009a9231b97a71114a1e5.1495663545.git.luto@kernel.org> References: <6760ae9459ba19657f8009a9231b97a71114a1e5.1495663545.git.luto@kernel.org> Message-ID: <20170526085225.GA28728@lst.de> On Wed, May 24, 2017@03:06:30PM -0700, Andy Lutomirski wrote: > This should at least make vendors less nervous about Linux's APST > policy. I'm not aware of any concrete bugs it would fix (although I > was hoping it would fix the Samsung/Dell quirk). > > Cc: stable at vger.kernel.org # v4.11 Just following a somewhat odd and arbitray policy from another driver that doesn't fix anything by itself certainly isn't stable material. And to be honest I'm not sure what applying it will gain us at all.