All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: <ferruh.yigit@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH] doc: notice for changes in kni structures
Date: Wed, 3 May 2017 08:50:54 -0700	[thread overview]
Message-ID: <20170503085054.06fafab8@xeon-e3> (raw)
In-Reply-To: <1493811091-26226-1-git-send-email-hemant.agrawal@nxp.com>

On Wed, 3 May 2017 17:01:31 +0530
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:

> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index a3e7c72..0c1ef2c 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -81,3 +81,10 @@ Deprecation Notices
>  
>    - ``rte_crpytodev_scheduler_mode_get``, replaced by ``rte_cryptodev_scheduler_mode_get``
>    - ``rte_crpytodev_scheduler_mode_set``, replaced by ``rte_cryptodev_scheduler_mode_set``
> +
> +* kni: additional functionality is planned to be added in kni to support mtu, macaddr,
> +  gso_size, promiscusity configuration.
> +  some of the kni structure will be changed to support additional functionality
> +  e.g  ``rte_kni_request`` to support promiscusity`` and mac_addr,
> +  ``rte_kni_mbu`` to support the configured gso_size,
> +  ``rte_kni_device_info`` and ``rte_kni_conf`` to also support mtu and macaddr.

Why are these exposed as something applications should care about?
The data structures in rte_kni_common.h are not an API

  reply	other threads:[~2017-05-03 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 11:31 [PATCH] doc: notice for changes in kni structures Hemant Agrawal
2017-05-03 15:50 ` Stephen Hemminger [this message]
2017-05-04 16:50   ` Ferruh Yigit
2017-05-08 10:00   ` Hemant Agrawal
2017-05-04 16:50 ` Ferruh Yigit
2017-05-08  9:46   ` Hemant Agrawal
2017-05-09 13:42     ` 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=20170503085054.06fafab8@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.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.