DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	David Hunt <david.hunt@intel.com>,
	dev@dpdk.org, "olivier.matz@6wind.com" <olivier.matz@6wind.com>,
	"viktorin@rehivetech.com" <viktorin@rehivetech.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] usages issue with external mempool
Date: Wed, 27 Jul 2016 15:35:18 +0200	[thread overview]
Message-ID: <2462423.EsoJo7cWtt@xps13> (raw)
In-Reply-To: <DB5PR04MB1605426413A7F750D3073004890F0@DB5PR04MB1605.eurprd04.prod.outlook.com>

2016-07-27 13:23, Hemant Agrawal:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-07-27 15:21, Jerin Jacob:
> > > If we agree on this then may be I can send the API deprecation notices
> > > for rte_mempool_create for v16.11
> > 
> > It would have been a lot better to send a patch during the 16.07 cycle to avoid
> > breaking again the API.
> > I'm afraid it will even be too late for the deprecation notice.
> 
> [Hemant] Yes! It is late. 
>  we can make these changes immediately after 16.07.

You cannot change the API in 16.11 without having a deprecation agreement
in 16.07.

  reply	other threads:[~2016-07-27 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 10:11 Hemant Agrawal
2016-07-27  9:51 ` Jerin Jacob
2016-07-27 10:00   ` Thomas Monjalon
2016-07-27 13:23     ` Hemant Agrawal
2016-07-27 13:35       ` Thomas Monjalon [this message]
2016-07-27 16:52         ` Hemant Agrawal
2016-07-28  7:09           ` Thomas Monjalon
2016-07-28  8:32   ` Olivier MATZ
2016-07-28 10:25     ` Jerin Jacob
2016-07-29 10:09     ` Hemant Agrawal

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=2462423.EsoJo7cWtt@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=olivier.matz@6wind.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=viktorin@rehivetech.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).