All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Arnon Warshavsky <arnon@qwilt.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	ranjit.menon@intel.com, anand.rawat@intel.com,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
	"O'Hare, Cathal" <cathal.ohare@intel.com>,
	Arnon Warshavsky <arnonw@qwilt.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce ABI change on eal and kni
Date: Wed, 08 May 2019 22:25:30 +0200	[thread overview]
Message-ID: <389361150.8XqXdKDBTD@xps> (raw)
In-Reply-To: <CAKy9EB1q+ZvGiLgw3V3AnS3KSO_hWmonxyOnpajJDz1neh3ojg@mail.gmail.com>

08/05/2019 22:22, Arnon Warshavsky:
> > I am preparing a deprecation notice for rte_eal_remote_launch
> > and rte_metrics_init.
> >
> hmm, I followed panic and not exit, so missed rte_metrics_init.
> rte_eal_remote_launch currently returns int. what deprecation goes there?

We probably need to add a new error code for rte_eal_remote_launch.
It is just a doxygen change, but it is part of the API.



      reply	other threads:[~2019-05-08 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 14:58 [dpdk-dev] [PATCH] doc: announce ABI change on eal and kni Arnon Warshavsky
2019-04-28 16:23 ` Stephen Hemminger
2019-04-29  9:28   ` Ferruh Yigit
2019-04-29 16:24     ` Stephen Hemminger
2019-04-29 17:19       ` Ferruh Yigit
2019-05-07  9:57         ` Arnon Warshavsky
2019-05-08 11:07           ` Thomas Monjalon
2019-05-08 20:22             ` Arnon Warshavsky
2019-05-08 20:25               ` 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=389361150.8XqXdKDBTD@xps \
    --to=thomas@monjalon.net \
    --cc=anand.rawat@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=arnon@qwilt.com \
    --cc=arnonw@qwilt.com \
    --cc=bruce.richardson@intel.com \
    --cc=cathal.ohare@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.