patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-stable] [PATCH 1/3] doc: fix typo in ipc doc
Date: Thu, 09 May 2019 16:41:57 +0200	[thread overview]
Message-ID: <5181364.ATmnSjObkD@xps> (raw)
In-Reply-To: <c5b98a67c6f0b66b3ef0534dc1b9ed553d4d7340.1556883753.git.anatoly.burakov@intel.com>

03/05/2019 13:50, Anatoly Burakov:
> The word "syncrhonous" appears twice. Fix it.
[...]
> --- a/doc/guides/prog_guide/multi_proc_support.rst
> +++ b/doc/guides/prog_guide/multi_proc_support.rst
> -For synchronous synchronous requests, the ``rte_mp_reply`` descriptor must also
> -be created. This is where the responses will be stored. The list of fields that
> -will be populated by IPC are as follows:
> +For synchronous requests, the ``rte_mp_reply`` descriptor must also be created.
> +This is where the responses will be stored. The list of fields that will be
> +populated by IPC are as follows:

For this reason, it is better to return to new line at the end of a sentence,
or after a comma. So the future patch will change only one line.
I will split this one.





  parent reply	other threads:[~2019-05-09 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 11:50 Anatoly Burakov
2019-05-03 11:50 ` [dpdk-stable] [PATCH 2/3] ipc: add warnings about not using ipc with memory API's Anatoly Burakov
2019-05-03 11:50 ` [dpdk-stable] [PATCH 3/3] ipc: add warnings about correct API usage Anatoly Burakov
2019-05-09 14:59   ` Thomas Monjalon
2019-05-03 19:03 ` [dpdk-stable] [dpdk-dev] [PATCH 1/3] doc: fix typo in ipc doc Rami Rosen
2019-05-09 14:41 ` Thomas Monjalon [this message]
2019-05-09 15:25 ` [dpdk-stable] " Mcnamara, John
2019-05-09 15:55   ` [dpdk-stable] [dpdk-dev] " 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=5181364.ATmnSjObkD@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=stable@dpdk.org \
    /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).