Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751687AbdFFS1s (ORCPT <rfc822;w@1wt.eu>);
        Tue, 6 Jun 2017 14:27:48 -0400
Received: from mail-wr0-f194.google.com ([209.85.128.194]:35454 "EHLO
        mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751494AbdFFS1q (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 6 Jun 2017 14:27:46 -0400
Subject: Re: [PATCH v5 0/9] Implement NVMe Namespace Descriptor Identification
To: Johannes Thumshirn <jthumshirn@suse.de>,
        Christoph Hellwig <hch@lst.de>, Keith Busch <keith.busch@intel.com>
Cc: Hannes Reinecke <hare@suse.de>, maxg@mellanox.com,
        Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
        Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
References: <20170606143617.32143-1-jthumshirn@suse.de>
From: Sagi Grimberg <sagi@grimberg.me>
Message-ID: <4f1616b4-5454-0486-5c03-0f3a1420b6c1@grimberg.me>
Date: Tue, 6 Jun 2017 21:27:35 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20170606143617.32143-1-jthumshirn@suse.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 161
Lines: 6


> * I'm not sure if I shall use nvme_ns_identifier_hdr or nvme_ns_id_desc

I was kinda hoping you will :(

I won't insist if people are fine with that as is...