From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: add Bus log type
Date: Mon, 19 Jun 2017 16:33:53 +0530 [thread overview]
Message-ID: <943050b9-9e57-970e-cbef-01afcdb9e3ff@nxp.com> (raw)
In-Reply-To: <1495604325-15743-1-git-send-email-shreyansh.jain@nxp.com>
Hello Thomas,
On Wednesday 24 May 2017 11:08 AM, Shreyansh Jain wrote:
> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> ---
> This was missed while adding the rte_bus code. (But, this is not a fix)
> Also, I couldn't find any maintainer listed for common/include/* code
> in MAINTAINERS, so, sending 'to' dev@ list.
>
>
> lib/librte_eal/common/include/rte_log.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_eal/common/include/rte_log.h b/lib/librte_eal/common/include/rte_log.h
> index 3419138..1e45e87 100644
> --- 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. */
>
> /* these log types can be used in an application */
> #define RTE_LOGTYPE_USER1 24 /**< User-defined log type 1. */
>
Just wanted to ping - is there something wrong/unacceptable about this?
-
Shreyansh
next prev parent reply other threads:[~2017-06-19 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 5:38 Shreyansh Jain
2017-06-19 11:03 ` Shreyansh Jain [this message]
2017-06-19 20:54 ` Thomas Monjalon
2017-07-02 5:31 ` Shreyansh Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=943050b9-9e57-970e-cbef-01afcdb9e3ff@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).