From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"viktorin@rehivetech.com" <viktorin@rehivetech.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: arm64: document DPDK application profiling methods
Date: Thu, 3 Nov 2016 12:30:27 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20264A10C@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1695172.8HmTq10QNC@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, October 26, 2016 9:07 PM
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Cc: dev@dpdk.org; jianbo.liu@linaro.org; viktorin@rehivetech.com
> Subject: Re: [dpdk-dev] [PATCH v2] doc: arm64: document DPDK application
> profiling methods
>
> 2016-10-05 14:13, Jerin Jacob:
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > ---
> > v2:
> > -Addressed ARM64 specific review comments(Suggested by Thomas)
>
> I feel more comments could be done, especially about formatting.
> You are adding a chapter Introduction without any other section of the
> same level.
> Some technical terms should be enclosed in backquotes.
>
> Please John, could you guide Jerin or provide an updated version?
Will do.
next prev parent reply other threads:[~2016-11-03 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 10:40 [dpdk-dev] [PATCH] " Jerin Jacob
2016-10-04 12:40 ` Thomas Monjalon
2016-10-04 12:45 ` Jan Viktorin
2016-10-05 8:43 ` [dpdk-dev] [PATCH v2] " Jerin Jacob
2016-10-26 20:07 ` Thomas Monjalon
2016-11-03 12:30 ` Mcnamara, John [this message]
2016-11-04 14:00 ` Mcnamara, John
2016-11-08 3:32 ` [dpdk-dev] [PATCH v3] " Jerin Jacob
2016-11-08 5:57 ` Jianbo Liu
2016-11-10 23:41 ` 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=B27915DBBA3421428155699D51E4CFE20264A10C@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas.monjalon@6wind.com \
--cc=viktorin@rehivetech.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).