From: "Jan Viktorin" <viktorin@rehivetech.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, thomas.monjalon@6wind.com
Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes for device objects
Date: Thu, 7 Apr 2016 19:27:45 +0200 [thread overview]
Message-ID: <20160407192745.3e354a99@pcviktorin.fit.vutbr.cz> (raw)
In-Reply-To: <1460043197-13707-1-git-send-email-david.marchand@6wind.com>
On Thu, 7 Apr 2016 17:33:17 +0200
David Marchand <david.marchand@6wind.com> wrote:
> Following discussions with Jan, here is a deprecation notice to prepare for
> hotplug and rte_device changes to come in 16.07.
>
> Signed-off-by: David Marchand <david.marchand@6wind.com>
> ---
Acked-by: Jan Viktorin <viktorin@rehivetech.com>
next prev parent reply other threads:[~2016-04-07 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:33 David Marchand
2016-04-07 15:46 ` Jan Viktorin
2016-04-07 17:00 ` David Marchand
2016-04-07 17:09 ` Jan Viktorin
2016-04-07 17:24 ` David Marchand
2016-04-07 17:27 ` Jan Viktorin [this message]
2016-04-08 9:35 ` Olivier Matz
2016-04-08 15:50 ` Thomas Monjalon
2016-04-10 10:05 ` 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=20160407192745.3e354a99@pcviktorin.fit.vutbr.cz \
--to=viktorin@rehivetech.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).