DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"Nicolau, Radu" <radu.nicolau@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: release notes 17.08, API change description
Date: Thu, 6 Jul 2017 15:25:36 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23ED23EE7@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1499333341-10875-1-git-send-email-radu.nicolau@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Radu Nicolau
> Sent: Thursday, July 6, 2017 10:29 AM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Nicolau, Radu <radu.nicolau@intel.com>
> Subject: [dpdk-dev] [PATCH v2] doc: release notes 17.08, API change
> description
> 
> Added API change description - moved bypass functions from the rte_ether
> library to ixgbe PMD
> 
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> 
> v2: Fixed style errors
> 
>  doc/guides/rel_notes/release_17_08.rst | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/release_17_08.rst
> b/doc/guides/rel_notes/release_17_08.rst
> index 842f46f..7c891b4 100644
> --- a/doc/guides/rel_notes/release_17_08.rst
> +++ b/doc/guides/rel_notes/release_17_08.rst
> @@ -144,6 +144,31 @@ API Changes
>     Also, make sure to start the actual text at the margin.
>     =========================================================
> 
> +* **Moved bypass functions from the rte_ether library to ixgbe PMD**
> +
> +  * The following rte_ether library APIs were removed:
> +
> +    * ``rte_eth_dev_bypass_event_show``
> +    * ``rte_eth_dev_bypass_event_store``
> +    * ``rte_eth_dev_bypass_init``
> +    * ``rte_eth_dev_bypass_state_set``
> +    * ``rte_eth_dev_bypass_state_show``
> +    * ``rte_eth_dev_bypass_ver_show``
> +    * ``rte_eth_dev_bypass_wd_reset``
> +    * ``rte_eth_dev_bypass_wd_timeout_show``
> +    * ``rte_eth_dev_wd_timeout_store``
> +
> +   * The following ixgbe PMD APIs were added:

The above line is indented slightly more than the previous "The following"
line. This causes the second list to be rendered in Html as a sub-list of
the first list. Which I'd guess isn't the intended behavior?

John

  reply	other threads:[~2017-07-06 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06  9:23 [dpdk-dev] [PATCH] " Radu Nicolau
2017-07-06  9:29 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2017-07-06 15:25   ` Mcnamara, John [this message]
2017-07-07  9:21   ` [dpdk-dev] [PATCH v3] " Radu Nicolau
2017-07-07 10:04     ` Mcnamara, John
2017-07-08 16:23     ` Thomas Monjalon
2017-07-10  9:15     ` [dpdk-dev] [PATCH v4] " Radu Nicolau
2017-07-10  9:18       ` [dpdk-dev] [PATCH v5] " Radu Nicolau
2017-07-10 11:39         ` [dpdk-dev] [PATCH v6] " Radu Nicolau
2017-07-10 19:26           ` Thomas Monjalon

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=B27915DBBA3421428155699D51E4CFE23ED23EE7@IRSMSX104.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=radu.nicolau@intel.com \
    --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).