From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 28C25C43441 for ; Mon, 26 Nov 2018 15:50:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EF8DF20664 for ; Mon, 26 Nov 2018 15:50:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EF8DF20664 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-block-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726448AbeK0Coz (ORCPT ); Mon, 26 Nov 2018 21:44:55 -0500 Received: from mga04.intel.com ([192.55.52.120]:21705 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726434AbeK0Coz (ORCPT ); Mon, 26 Nov 2018 21:44:55 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Nov 2018 07:50:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,282,1539673200"; d="scan'208";a="94186030" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga006.jf.intel.com with ESMTP; 26 Nov 2018 07:50:25 -0800 Date: Mon, 26 Nov 2018 08:47:23 -0700 From: Keith Busch To: Sagi Grimberg Cc: "linux-nvme@lists.infradead.org" , "linux-block@vger.kernel.org" , "netdev@vger.kernel.org" , Christoph Hellwig , "David S. Miller" Subject: Re: [PATCH nvme-cli v3 15/13] nvme: Add TCP transport Message-ID: <20181126154723.GP26707@localhost.localdomain> References: <20181122015615.15763-1-sagi@grimberg.me> <20181122015615.15763-16-sagi@grimberg.me> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181122015615.15763-16-sagi@grimberg.me> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org The cli parts good to me. Is there any forseeable issue if I apply these ahead of the kernel integration? I don't see any, but just want to confirm since its all in one series. From mboxrd@z Thu Jan 1 00:00:00 1970 From: keith.busch@intel.com (Keith Busch) Date: Mon, 26 Nov 2018 08:47:23 -0700 Subject: [PATCH nvme-cli v3 15/13] nvme: Add TCP transport In-Reply-To: <20181122015615.15763-16-sagi@grimberg.me> References: <20181122015615.15763-1-sagi@grimberg.me> <20181122015615.15763-16-sagi@grimberg.me> Message-ID: <20181126154723.GP26707@localhost.localdomain> The cli parts good to me. Is there any forseeable issue if I apply these ahead of the kernel integration? I don't see any, but just want to confirm since its all in one series.