From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, shreyansh.jain@nxp.com,
akhil.goyal@nxp.com
Subject: Re: [dpdk-dev] [PATCH 0/8] NXP DPAA2 compilation and runtime fixes
Date: Fri, 14 Jul 2017 15:49:18 +0200 [thread overview]
Message-ID: <5506190.GmmlQzotSk@xps> (raw)
In-Reply-To: <1499784959-8598-1-git-send-email-hemant.agrawal@nxp.com>
11/07/2017 16:55, Hemant Agrawal:
> This patch series add support for:
> [1-2] GCC 7.1 compilation issue
> [3-4] Compilation with all debug mode enabled
> [5-7] Run time issues obseved over RC1
> [8] adding newline char in RTE_LOG
>
> Hemant Agrawal (8):
> crypto/dpaa2_sec: remove GCC 7.1 compilation error
> net/dpaa2: fix flow control switch case break
> bus/fslmc: fixes compilation in debug mode
> event/dpaa2: enable debug mode compilation
> bus/fslmc: set the dpaa2 device name
> bus/fslmc: align the object name log to real resource names
> config: enable virtual IOVA by default for DPAA2
> drivers: add newline in RTE LOG usages in dpaa2
Applied, thanks
prev parent reply other threads:[~2017-07-14 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 14:55 Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 1/8] crypto/dpaa2_sec: remove GCC 7.1 compilation error Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 2/8] net/dpaa2: fix flow control switch case break Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 3/8] bus/fslmc: fixes compilation in debug mode Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 4/8] event/dpaa2: enable debug mode compilation Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 5/8] bus/fslmc: set the dpaa2 device name Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 6/8] bus/fslmc: align the object name log to real resource names Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 7/8] config: enable virtual IOVA by default for DPAA2 Hemant Agrawal
2017-07-11 14:55 ` [dpdk-dev] [PATCH 8/8] drivers: add newline in RTE LOG usages in dpaa2 Hemant Agrawal
2017-07-14 13:49 ` Thomas Monjalon [this message]
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=5506190.GmmlQzotSk@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=shreyansh.jain@nxp.com \
/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).