From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [PATCH] eal: add Bus log type
Date: Sun, 2 Jul 2017 11:01:41 +0530
Message-ID: <6f67d562-e9e3-5a17-84d3-9685dad7b701@nxp.com>
References: <1495604325-15743-1-git-send-email-shreyansh.jain@nxp.com>
 <943050b9-9e57-970e-cbef-01afcdb9e3ff@nxp.com> <4669455.PggrvpOhcS@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc: <dev@dpdk.org>
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from NAM01-BN3-obe.outbound.protection.outlook.com
 (mail-bn3nam01on0070.outbound.protection.outlook.com [104.47.33.70])
 by dpdk.org (Postfix) with ESMTP id 1212C374
 for <dev@dpdk.org>; Sun,  2 Jul 2017 07:22:39 +0200 (CEST)
In-Reply-To: <4669455.PggrvpOhcS@xps>
Content-Language: en-US
List-Id: DPDK patches and discussions <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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Tuesday 20 June 2017 02:24 AM, Thomas Monjalon wrote:
> 19/06/2017 13:03, Shreyansh Jain:
>>> --- a/lib/librte_eal/common/include/rte_log.h
>>> +++ b/lib/librte_eal/common/include/rte_log.h
>>> @@ -87,6 +87,7 @@ extern struct rte_logs rte_logs;
>>>   #define RTE_LOGTYPE_CRYPTODEV 17 /**< Log related to cryptodev. */
>>>   #define RTE_LOGTYPE_EFD       18 /**< Log related to EFD. */
>>>   #define RTE_LOGTYPE_EVENTDEV  19 /**< Log related to eventdev. */
>>> +#define RTE_LOGTYPE_BUS       20 /**< Log related to Bus. */
>>
>> Just wanted to ping - is there something wrong/unacceptable about this?
> 
> Sorry for not replying before.

And I am sorry for spotting your reply so late.

> 
> The strange thing is that it is not used.

Yes, because somehow I forgot this while pushing bus/fslmc. I (had (*)) plan to change this for bus/fslmc in subsequent patches.

> At least, the existing bus logs should be converted.
> I've spotted few lines in drivers/bus/fslmc/.
> 
> And more importantly, we must switch to the new dynamic types
> using rte_log_register().
> 

(*)
ok. In which case, this patch would become redundant. I will add support for this in dpaa (and dpaa2 driver, next).

-
Shreyansh