DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] doc: fix typo in ipc doc
Date: Thu, 09 May 2019 17:55:32 +0200	[thread overview]
Message-ID: <6381173.Jt6ZCSykyt@xps> (raw)
Message-ID: <20190509155532.b9ZJ1ZU1dG9GkCy1bypyVcS0KWIJ3GvM-1RBRSl8TXI@z> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F615E2F@IRSMSX103.ger.corp.intel.com>

09/05/2019 17:25, Mcnamara, John:
> From: Burakov, Anatoly
> > The word "syncrhonous" appears twice. Fix it.

"synchronous" ;)

Fixes: e22266669e86 ("doc: add IPC guide")

> Acked-by: John McNamara <john.mcnamara@intel.com>

Series applied, thanks




  parent reply	other threads:[~2019-05-09 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 11:50 Anatoly Burakov
2019-05-03 11:50 ` Anatoly Burakov
2019-05-03 11:50 ` [dpdk-dev] [PATCH 2/3] ipc: add warnings about not using ipc with memory API's Anatoly Burakov
2019-05-03 11:50   ` Anatoly Burakov
2019-05-03 11:50 ` [dpdk-dev] [PATCH 3/3] ipc: add warnings about correct API usage Anatoly Burakov
2019-05-03 11:50   ` Anatoly Burakov
2019-05-09 14:59   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-05-09 14:59     ` Thomas Monjalon
2019-05-03 19:03 ` [dpdk-dev] [PATCH 1/3] doc: fix typo in ipc doc Rami Rosen
2019-05-03 19:03   ` Rami Rosen
2019-05-09 14:41 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-05-09 14:41   ` Thomas Monjalon
2019-05-09 15:25 ` [dpdk-dev] " Mcnamara, John
2019-05-09 15:25   ` Mcnamara, John
2019-05-09 15:55   ` Thomas Monjalon [this message]
2019-05-09 15:55     ` 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=6381173.Jt6ZCSykyt@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).