From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 4/5] doc: update the dpaaX platform guides
Date: Thu, 2 May 2019 15:56:36 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F60BFAD@IRSMSX103.ger.corp.intel.com> (raw)
Message-ID: <20190502155636.Ol-ufP_mcYkUO_zrzWEhGx8fIll0UYYA22MF1XD5NxY@z> (raw)
In-Reply-To: <20190424114520.23655-4-hemant.agrawal@nxp.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Hemant Agrawal
> Sent: Wednesday, April 24, 2019 12:45 PM
> To: dev@dpdk.org
> Cc: shreyansh.jain@nxp.com
> Subject: [dpdk-dev] [PATCH 4/5] doc: update the dpaaX platform guides
>
> Update the dpaa platform guides with latest SDK dependency.
>
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2019-05-02 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 11:45 [dpdk-dev] [PATCH 1/5] raw/dpaa2_qdma: fix spin lock release condition Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-04-24 11:45 ` [dpdk-dev] [PATCH 2/5] raw/dpaa2_qdma: fix spin lock Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-04-24 11:45 ` [dpdk-dev] [PATCH 3/5] net/dpaa2: fix the loopback spelling Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-04-24 11:45 ` [dpdk-dev] [PATCH 4/5] doc: update the dpaaX platform guides Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-05-02 15:56 ` Mcnamara, John [this message]
2019-05-02 15:56 ` Mcnamara, John
2019-04-24 11:45 ` [dpdk-dev] [PATCH 5/5] raw/dpaa2_cmdif: remove driver name assignment Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-05-02 21:31 ` [dpdk-dev] [dpdk-stable] [PATCH 1/5] raw/dpaa2_qdma: fix spin lock release condition Thomas Monjalon
2019-05-02 21:31 ` 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=B27915DBBA3421428155699D51E4CFE23F60BFAD@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--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).