DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Arnon Warshavsky <arnon@qwilt.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce API change to remove exit calls in libs
Date: Thu, 9 May 2019 09:34:20 +0200	[thread overview]
Message-ID: <CAJFAV8zOPipG_jy_d0xE61JeC2SZdivTJSHacjQaU4OsJQBAZA@mail.gmail.com> (raw)
In-Reply-To: <20190508205413.31134-1-thomas@monjalon.net>

On Wed, May 8, 2019 at 10:54 PM Thomas Monjalon <thomas@monjalon.net> wrote:

> Two public functions from EAL and metrics libraries need to return
> some new error codes instead of calling rte_panic or rte_exit.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  doc/guides/rel_notes/deprecation.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index b47c8c254..e61278429 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -20,6 +20,9 @@ Deprecation Notices
>  * kvargs: The function ``rte_kvargs_process`` will get a new parameter
>    for returning key match count. It will ease handling of no-match case.
>
> +* eal: The function ``rte_eal_remote_launch`` will return new error codes
> +  after read or write error on the pipe, instead of calling ``rte_panic``.
> +
>

Nit: do we need error codes ? or only a single new error code ?


 * eal: both declaring and identifying devices will be streamlined in
> v18.11.
>    New functions will appear to query a specific port from buses, classes
> of
>    device and device drivers. Device declaration will be made coherent
> with the
> @@ -82,3 +85,6 @@ Deprecation Notices
>  * cryptodev: the ``uint8_t *data`` member of ``key`` structure in the
> xforms
>    structure (``rte_crypto_cipher_xform``, ``rte_crypto_auth_xform``, and
>    ``rte_crypto_aead_xform``) will be changed to ``const uint8_t *data``.
> +
> +* metrics: The function ``rte_metrics_init`` will have a non-void return
> +  in order to notify errors instead of calling ``rte_exit``.
> --
> 2.21.0
>
>
Acked-by: David Marchand <david.marchand@redhat.com>

-- 
David Marchand

  parent reply	other threads:[~2019-05-09  7:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 20:54 Thomas Monjalon
2019-05-08 20:54 ` Thomas Monjalon
2019-05-09  5:31 ` Arnon Warshavsky
2019-05-09  5:31   ` Arnon Warshavsky
2019-05-13 20:54   ` Thomas Monjalon
2019-05-13 20:54     ` Thomas Monjalon
2019-05-09  7:34 ` David Marchand [this message]
2019-05-09  7:34   ` David Marchand
2019-05-09  7:38   ` Thomas Monjalon
2019-05-09  7:38     ` Thomas Monjalon
2019-05-09 14:55 ` Ferruh Yigit
2019-05-09 14:55   ` Ferruh Yigit

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=CAJFAV8zOPipG_jy_d0xE61JeC2SZdivTJSHacjQaU4OsJQBAZA@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=arnon@qwilt.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).