DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Rosen, Rami" <rami.rosen@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Rosen, Rami" <rami.rosen@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix an error in DPDK programmers's guide	(EAL)
Date: Thu, 2 Nov 2017 17:07:10 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EDEFEFD@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1509161813-18946-1-git-send-email-rami.rosen@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Saturday, October 28, 2017 4:37 AM
> To: dev@dpdk.org
> Cc: Rosen, Rami <rami.rosen@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: fix an error in DPDK programmers's guide
> (EAL)
> 
> Fix an error in DPDK programmer's guide (EAL section): it should be
> rte_thread_get_affinity() instead of rte_pthread_get_affinity().
> 
> Signed-off-by: Rami Rosen <rami.rosen@intel.com>

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

  reply	other threads:[~2017-11-02 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  3:36 Rami Rosen
2017-11-02 17:07 ` Mcnamara, John [this message]
2017-11-13  5:33   ` 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=B27915DBBA3421428155699D51E4CFE23EDEFEFD@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=rami.rosen@intel.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).