From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <remy.horton@intel.com>
Received: from mga14.intel.com (mga14.intel.com [192.55.52.115])
 by dpdk.org (Postfix) with ESMTP id A1DF5C45E
 for <dev@dpdk.org>; Wed, 15 Jun 2016 11:32:55 +0200 (CEST)
Received: from fmsmga001.fm.intel.com ([10.253.24.23])
 by fmsmga103.fm.intel.com with ESMTP; 15 Jun 2016 02:32:53 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.26,475,1459839600"; d="scan'208";a="987850823"
Received: from rhorton-mobl.ger.corp.intel.com (HELO [163.33.228.155])
 ([163.33.228.155])
 by fmsmga001.fm.intel.com with ESMTP; 15 Jun 2016 02:32:49 -0700
Message-ID: <576120C1.30905@intel.com>
Date: Wed, 15 Jun 2016 10:32:49 +0100
From: Remy Horton <remy.horton@intel.com>
Organization: Intel Shannon Limited
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Thomas Monjalon <thomas.monjalon@6wind.com>
CC: dev@dpdk.org
References: <1465982245-1162-1-git-send-email-remy.horton@intel.com>
 <1465982245-1162-2-git-send-email-remy.horton@intel.com>
 <54322711.BUndy8Ap0U@xps13>
In-Reply-To: <54322711.BUndy8Ap0U@xps13>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] [PATCH v3 1/3] eal: export keepalive state
	enumerations
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2016 09:32:56 -0000


On 15/06/2016 10:27, Thomas Monjalon wrote:
[..]
> I'm concerned about the namespace here.
> RTE_UNUSED and others have a chance to not be unique enough.
> Is it possible to have a longer prefix like RTE_KA_ or RTE_STATE_
> or RTE_KA_STATE_?
>

Good point - I'll go with RTE_KA_STATE_ as it is most descriptive.

..Remy