DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: John McNamara <john.mcnamara@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] doc: add device specific API
Date: Mon, 30 Jan 2017 21:25:34 +0100	[thread overview]
Message-ID: <1631657.ULgr08teK2@xps13> (raw)
In-Reply-To: <3191673.F6sSxlxfS2@xps13>

2017-01-30 21:21, Thomas Monjalon:
> 2017-01-30 18:27, Ferruh Yigit:
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> 
> Applied, thanks

Actually no, there are a lot of doxygen errors in ixgbe and i40e API.
I cannot be merged as is.

  reply	other threads:[~2017-01-30 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 12:27 [dpdk-dev] [PATCH] doc: add PMD " Ferruh Yigit
2017-01-30 17:57 ` Thomas Monjalon
2017-01-30 18:24 ` [dpdk-dev] [PATCH v2] doc: add device " Ferruh Yigit
2017-01-30 18:27   ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2017-01-30 20:21     ` Thomas Monjalon
2017-01-30 20:25       ` Thomas Monjalon [this message]
2017-01-30 20:27         ` Ferruh Yigit
2017-01-30 20:36           ` 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=1631657.ULgr08teK2@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@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).