Received: by 10.192.165.156 with SMTP id m28csp562435imm; Tue, 17 Apr 2018 15:20:28 -0700 (PDT) X-Google-Smtp-Source: AIpwx49lI4mGXjIkSPwX11k/STeG17fmZSwVfobmenTv/8UhgtoLnYdi45/AsztcHSlaeDyklq/c X-Received: by 10.98.68.135 with SMTP id m7mr3484939pfi.57.1524003628567; Tue, 17 Apr 2018 15:20:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524003628; cv=none; d=google.com; s=arc-20160816; b=jFMPEvYJQWeDZ059e8YWAW4LWaGgSFBgT8BO5MtTuH3wB15Htpg12QQx3jxfSnADzU Au1FFhWKxe/TVqJsu9ZcBCgtLo5sUygJOKamIgSg6TPncbpGFv573sxc/MsEE3vGs35L pp7y3DCzhV3BVxqw7S7zoopaZLVXlh4yBI/pIqYXg2t9Tcqgp7pl49bVj04di9GTBtyA T1KlgcMJPVCSrWUoUSTD6rPG3l/unpXWPbmSjam89utivk0ym86hPK4CrrJvlLBc7sSs wC6HCcqkAeOJkIoAnp+TKhnam5m5hvqu1aSD0SHLhnbj7Suzt+0OzQqiiWw6DY/FDr/h smvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=YqCXD2LL0po9JgRzdIgOBHAhiv7XXPGmaS98eVySIEU=; b=ox0qRDTqoDS0ED3YAukir4W5k5XukmzlQpRH0B8fn0LLPDErW9xk/lPi70eolokcQ6 u+OTIvMtUV98feWYxLBXugr76loGT6fI7gKlOzS5cdclnmOoejHOOldybPCsOUAtNSn4 hcOodVs4O6jJ/66SFTZ+2rGfiT5y+UYe/zjIo4dkgvfp0jA8GUvfVDfJFkNBpbbghDSv lrO2U0mhD0v/bDnLbCy5rWsNTjxOWRlUUmdDZuBDKuvKDhseQGVMwo2Cyu2Zgi+9HAcB PuvB+aw9rxjzMS7hcERiNw0h5gkeiCDUUoKBp5o0fs+kdurS0Wc7I4pYdRxshmjzmQX6 Hh8g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h2si4425099pfb.111.2018.04.17.15.20.14; Tue, 17 Apr 2018 15:20:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752899AbeDQWSZ (ORCPT + 99 others); Tue, 17 Apr 2018 18:18:25 -0400 Received: from mga04.intel.com ([192.55.52.120]:28916 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752319AbeDQWSY (ORCPT ); Tue, 17 Apr 2018 18:18:24 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2018 15:18:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,464,1517904000"; d="scan'208";a="47750345" Received: from unknown (HELO localhost.localdomain) ([10.232.112.44]) by fmsmga001.fm.intel.com with ESMTP; 17 Apr 2018 15:18:23 -0700 Date: Tue, 17 Apr 2018 16:19:27 -0600 From: Keith Busch To: Jens Axboe Cc: Matias =?iso-8859-1?Q?Bj=F8rling?= , Wei Xu , linux-nvme@lists.infradead.org, javier@cnexlabs.com, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvme: lightnvm: add granby support Message-ID: <20180417221926.GH11513@localhost.localdomain> References: <1523930112-7402-1-git-send-email-wxu@cnexlabs.com> <6e50972d-f806-52ac-7983-2642bd211afa@lightnvm.io> <20180417220901.GG11513@localhost.localdomain> <6701f433-e865-5a17-f1c7-4c0e0c5effaa@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6701f433-e865-5a17-f1c7-4c0e0c5effaa@kernel.dk> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2018 at 04:15:38PM -0600, Jens Axboe wrote: > >> Looks good to me. > >> > >> Reviewed-by: Matias Bj?rling > >> > >> Keith, when convenient can you pick this up for 4.18? > > > > This looks safe for 4.17-rc2, no? Unless you want to wait for the next > > release. > > It should wait for the next release, it's not a fix. Okay, queued up for the next release. I'll wait a few more rc's before posting the nvme-4.18 branch.