DPDK patches and discussions
 help / color / mirror / Atom feed
From: Reshma Pattan <reshma.pattan@intel.com>
To: dev@dpdk.org
Cc: Reshma Pattan <reshma.pattan@intel.com>,
	David Hunt <david.hunt@intel.com>
Subject: [PATCH v3] doc: add removal note for power empty poll API
Date: Fri,  7 Oct 2022 14:40:34 +0100	[thread overview]
Message-ID: <20221007134034.498762-1-reshma.pattan@intel.com> (raw)
In-Reply-To: <20221005084419.480317-1-reshma.pattan@intel.com>

Add removal note for experimental empty poll API.

CC: David Hunt <david.hunt@intel.com>

Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
Acked-by: David Hunt <david.hunt@intel.com>
---
 doc/guides/prog_guide/power_man.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/guides/prog_guide/power_man.rst b/doc/guides/prog_guide/power_man.rst
index 98cfd3c1f3..3b0c3373a1 100644
--- a/doc/guides/prog_guide/power_man.rst
+++ b/doc/guides/prog_guide/power_man.rst
@@ -192,6 +192,14 @@ User Cases
 ----------
 The mechanism can applied to any device which is based on polling. e.g. NIC, FPGA.
 
+
+Removal Note
+------------
+
+The experimental empty poll APIs will be removed from the library in a future
+DPDK release.
+
+
 Ethernet PMD Power Management API
 ---------------------------------
 
-- 
2.31.1


  parent reply	other threads:[~2022-10-07 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 15:22 [PATCH] " Reshma Pattan
2022-08-30  9:23 ` Hunt, David
2022-10-05  8:44 ` [PATCH v2] " Reshma Pattan
2022-10-05 12:27   ` Thomas Monjalon
2022-10-07 13:54     ` Pattan, Reshma
2022-10-07 13:40   ` Reshma Pattan [this message]
2022-10-31 15:26     ` [PATCH v3] " Thomas Monjalon
2022-11-02 12:35       ` Pattan, Reshma
2022-11-02 12:31     ` [PATCH v4] doc: add removal warning " Reshma Pattan
2022-11-02 12:41       ` [PATCH v5] " Reshma Pattan
2022-11-15 15:35         ` 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=20221007134034.498762-1-reshma.pattan@intel.com \
    --to=reshma.pattan@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    /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).