Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S971133AbdDTQV5 (ORCPT ); Thu, 20 Apr 2017 12:21:57 -0400 Received: from mga03.intel.com ([134.134.136.65]:29479 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S971107AbdDTQUf (ORCPT ); Thu, 20 Apr 2017 12:20:35 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,225,1488873600"; d="scan'208";a="959231323" Date: Thu, 20 Apr 2017 12:29:25 -0400 From: Keith Busch To: Sagi Grimberg Cc: Jens Axboe , Andy Lutomirski , "linux-kernel@vger.kernel.org" , Kai-Heng Feng , linux-nvme@lists.infradead.org, Christoph Hellwig Subject: Re: [PATCH v2 0/2] nvme APST quirk updates, take two Message-ID: <20170420162925.GB25259@localhost.localdomain> References: <9cd43193-af6b-2cb1-3951-5fa569bf1f31@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 757 Lines: 21 On Thu, Apr 20, 2017 at 07:15:15PM +0300, Sagi Grimberg wrote: > > > > Hi Jens- > > > > > > These are just the quirk updates, split out. The patches are > > > unchanged. > > > > > > I think that, even if we want to apply a broader quirk for 4.11, we > > > should still apply these so that we can cleanly revert the broader > > > quirk later. IOW, let's get the known regressions fixed before we > > > get too excited about the unknown regressions. > > > > This looks good to me, and 4.11 appropriate. I'll expedite this > > through the block tree, if Keith/Sagi/Christoph agrees on this > > being the right approach for 4.11. > > I'm perfectly fine with this going to 4.11 All good with me as well. Reviewed-by: Keith Busch