From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Xingyou Chen <niatlantice@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix some typos in prog_guide
Date: Sun, 11 Jun 2017 08:42:50 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23ECEE57A@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20170608020924.4203-1-niatlantice@gmail.com>
> -----Original Message-----
> From: Xingyou Chen [mailto:niatlantice@gmail.com]
> Sent: Thursday, June 8, 2017 3:09 AM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: dev@dpdk.org; Xingyou Chen <niatlantice@gmail.com>
> Subject: [PATCH] doc: fix some typos in prog_guide
>
> Signed-off-by: Xingyou Chen <niatlantice@gmail.com>
> ---
> doc/guides/prog_guide/perf_opt_guidelines.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/prog_guide/perf_opt_guidelines.rst
> b/doc/guides/prog_guide/perf_opt_guidelines.rst
> index 7c24aa485..286bf9837 100644
> --- a/doc/guides/prog_guide/perf_opt_guidelines.rst
> +++ b/doc/guides/prog_guide/perf_opt_guidelines.rst
> @@ -38,7 +38,7 @@ Performance Optimization Guidelines Introduction
> ------------
>
> -The following sections describe optimizations used in the DPDK and
> optimizations that should be considered for a new applications.
> +The following sections describe optimizations used in DPDK and
> optimizations that should be considered for new applications.
>
> They also highlight the performance-impacting coding techniques that
> should, and should not be, used when developing an application using the
> DPDK.
Just to note on the first typo that "the DPDK" is actually
correct and the original documentation was written like that and
some people say it that way. In that usage I think the definite
article is being associated with the "Kit" part of the spelled
out acronym. However, in practice many people now use DPDK as a
proper noun and omit the definite article. Either way is fine
with me.
Acked-by: John McNamara <john.mcnamara@intel.com>
next parent reply other threads:[~2017-06-11 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170608020924.4203-1-niatlantice@gmail.com>
2017-06-11 8:42 ` Mcnamara, John [this message]
2017-06-08 2:14 Xingyou Chen
2017-06-11 8:46 ` Mcnamara, John
2017-07-02 17:25 ` 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=B27915DBBA3421428155699D51E4CFE23ECEE57A@IRSMSX104.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=niatlantice@gmail.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).