From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Bernard Iremonger <bernard.iremonger@intel.com>,
dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce API and ABI change for ethdev
Date: Tue, 14 Feb 2017 08:47:12 +0530 [thread overview]
Message-ID: <20170214031712.GA3131@localhost.localdomain> (raw)
In-Reply-To: <1783105.gzj7YZmmC4@xps13>
On Mon, Feb 13, 2017 at 06:57:20PM +0100, Thomas Monjalon wrote:
> 2017-01-05 15:25, Bernard Iremonger:
> > In 17.05 nine rte_eth_dev_* functions will be removed from
> > librte_ether, renamed and moved to the ixgbe PMD.
> >
> > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
>
> "ixgbe bypass" should be in the title and the description.
> I'll reword to:
>
> doc: announce move of ethdev bypass function to ixgbe API
>
> In 17.05, nine rte_eth_dev_* functions for bypass control,
> and implemented only in ixgbe, will be removed from ethdev,
> renamed and moved to the ixgbe PMD-specific API.
>
> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2017-02-14 3:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 10:44 [dpdk-dev] [PATCH v1] " Bernard Iremonger
2017-01-05 13:31 ` Thomas Monjalon
2017-01-05 14:40 ` Iremonger, Bernard
2017-01-05 15:25 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2017-02-13 17:57 ` Thomas Monjalon
2017-02-14 3:17 ` Jerin Jacob [this message]
2017-02-14 10:33 ` Iremonger, Bernard
2017-02-14 19:37 ` Thomas Monjalon
2017-07-12 7:58 [dpdk-dev] [PATCH] " Zhiyong Yang
2017-08-04 5:27 ` [dpdk-dev] [PATCH v2] " Zhiyong Yang
2017-08-04 6:56 ` Remy Horton
2017-08-05 10:34 ` Yang, Zhiyong
2017-08-07 3:07 ` Yang, Zhiyong
2017-08-07 11:04 ` Thomas Monjalon
2017-08-07 15:20 ` Shahaf Shuler
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=20170214031712.GA3131@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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).