DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Nipun Gupta <nipun.gupta@nxp.com>,
	thomas@monjalon.net, jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, santosh.shukla@caviumnetworks.com,
	shreyansh.jain@nxp.com, sunil.kori@nxp.com
Subject: Re: [dpdk-dev] [PATCH 3/4] event/dpaa: rename dpaa vdev with dpaa1
Date: Mon, 5 Feb 2018 17:26:12 +0530	[thread overview]
Message-ID: <46d467dd-8194-a1a3-f008-82b39ba9da65@nxp.com> (raw)
In-Reply-To: <1517808117-28562-3-git-send-email-nipun.gupta@nxp.com>

On 2/5/2018 10:51 AM, Nipun Gupta wrote:
> DPAA2 eventdev is named as event_dpaa2 which conflicts with
> event_dpaa when both are compiled in together. So event_dpaa
> is required to renamed.
> 
> Fixes: 1ee9569576f6 ("config: enable dpaaX drivers for generic ARMv8")
> 
> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> ---
>   doc/guides/eventdevs/dpaa.rst      | 6 +++---
>   drivers/event/dpaa/dpaa_eventdev.h | 2 +-
>   2 files changed, 4 insertions(+), 4 deletions(-)
> 

Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
<snip..>

  reply	other threads:[~2018-02-05 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  5:21 [dpdk-dev] [PATCH 1/4] bus/fslmc: fix registering dpaa2 mempool ops Nipun Gupta
2018-02-05  5:21 ` [dpdk-dev] [PATCH 2/4] bus/dpaa: fix registering dpaa " Nipun Gupta
2018-02-05  5:36   ` santosh
2018-02-05  6:31   ` Shreyansh Jain
2018-02-05  5:21 ` [dpdk-dev] [PATCH 3/4] event/dpaa: rename dpaa vdev with dpaa1 Nipun Gupta
2018-02-05 11:56   ` Hemant Agrawal [this message]
2018-02-05  5:21 ` [dpdk-dev] [PATCH 4/4] event/dpaa: fix portal allocation Nipun Gupta
2018-02-05 11:53   ` Hemant Agrawal
2018-02-05  6:32 ` [dpdk-dev] [PATCH 1/4] bus/fslmc: fix registering dpaa2 mempool ops Shreyansh Jain
2018-02-05 23:44   ` Thomas Monjalon

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=46d467dd-8194-a1a3-f008-82b39ba9da65@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=nipun.gupta@nxp.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=sunil.kori@nxp.com \
    --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).