Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751313AbdFEFcF (ORCPT ); Mon, 5 Jun 2017 01:32:05 -0400 Received: from verein.lst.de ([213.95.11.211]:37993 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751249AbdFEFcE (ORCPT ); Mon, 5 Jun 2017 01:32:04 -0400 Date: Mon, 5 Jun 2017 07:32:03 +0200 From: Christoph Hellwig To: Johannes Thumshirn Cc: Christoph Hellwig , Sagi Grimberg , Keith Busch , Hannes Reinecke , maxg@mellanox.com, Linux NVMe Mailinglist , Linux Kernel Mailinglist Subject: Re: [PATCH v4 0/8] Implement NVMe Namespace Descriptor Identification Message-ID: <20170605053203.GB19480@lst.de> References: <20170604103649.22130-1-jthumshirn@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170604103649.22130-1-jthumshirn@suse.de> 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 Content-Length: 422 Lines: 11 On Sun, Jun 04, 2017 at 12:36:41PM +0200, Johannes Thumshirn wrote: > The Namespace Identification Descriptor list is the only way a target > can identify itself via the newly introduced UUID to the host (instead > of the EUI-64 or NGUID). s/instead/in addition/ > While I was already touching the relevant code paths, I decided to > also include the EUI-64 in the 'Identify Namespace' command response. Not anymore :)