DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: announce rte_devargs changes in 17.11
Date: Tue, 08 Aug 2017 01:18:28 +0200	[thread overview]
Message-ID: <2478236.nqvkQR7p5U@xps> (raw)
In-Reply-To: <1501853399-17487-1-git-send-email-gaetan.rivet@6wind.com>

04/08/2017 15:29, Gaetan Rivet:
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> ---
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> +* eal: several API and ABI changes are planned for ``rte_devargs`` in v17.11.
> +  The format of device command line parameters will change. The bus will need
> +  to be explicitly stated in the device declaration. The enum ``rte_devtype``
> +  was used to identify a bus and will disappear.
> +  The structure ``rte_devargs`` will change.
> +  The ``rte_devargs_list`` will be made private.
> +  The following functions are deprecated starting from 17.08 and will either be
> +  modified or removed in 17.11:
> +
> +  - ``rte_eal_devargs_add``
> +  - ``rte_eal_devargs_type_count``

Acked-by: Thomas Monjalon <thomas@monjalon.net>

This kind of change has already been suggested by Jan Blunck:
	http://dpdk.org/ml/archives/dev/2017-July/070729.html
	http://dpdk.org/ml/archives/dev/2017-July/071054.html

It is very important to continue progressing on device syntax and
bus rework during 17.11.

Applied

      reply	other threads:[~2017-08-07 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 13:29 Gaetan Rivet
2017-08-07 23:18 ` 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=2478236.nqvkQR7p5U@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@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).