DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Laatz, Kevin" <kevin.laatz@intel.com>
Cc: dev@dpdk.org, "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: include note for pci address naming in ip pipeline
Date: Sun, 05 Aug 2018 20:28:39 +0200	[thread overview]
Message-ID: <1647983.1e1N7qbnXe@xps> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891268E782866@IRSMSX107.ger.corp.intel.com>

01/08/2018 19:47, Dumitrescu, Cristian:
> > 20/07/2018 15:09, Kevin Laatz:
> > > Add a note to the 'link' command in the IP Pipeline documentation
> > > specifying the PCI device name format required to run the application.
> > >
> > > Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
> 
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Applied, thanks

      reply	other threads:[~2018-08-05 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 13:09 Kevin Laatz
2018-08-01 15:56 ` Thomas Monjalon
2018-08-01 17:47   ` Dumitrescu, Cristian
2018-08-05 18:28     ` Thomas Monjalon [this message]

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=1647983.1e1N7qbnXe@xps \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@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).