patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Hunt <>
Subject: [dpdk-stable] [PATCH v4] lib/power: remove set env deprecation notice
Date: Tue, 27 Oct 2020 13:24:13 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Remove notice announcing an already-implemented change.

In 19.05, rte_power_set_env was changed to return -1 in cases where
the envorinment was already set up, and for the same release, a
deprecation notice was added for the following commit:
'commit 5a5f3178d4a8 ("power: return error when environment already set")'
This patch removes that notice.

The API change was tested by calling rte_power_set_env twice. The first
call succeeded, and the second call failed, as expected.

Signed-off-by: David Hunt <>


v1 initial version (with typo in the title)
v2 fix typo but forgot --in-reply-to
v3 add -in-reply-to
v4 add in version info, and cc stable in case it needs to be backported

Note: CC'ing stable in case the deprecation notice should also be removed
from 19.11. It looks to me like the patch making the change and the patch
adding the notice were both added in 19.11, so the notice is no longer
needed in that verion. I didn't add a Fixes line to this patch as I believe
the notice was correct, just adding both fix and notice in the same version
was not strictly the right thing to have done at the time.
 doc/guides/rel_notes/deprecation.rst | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 76a83968c..ed82df52a 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -172,11 +172,6 @@ Deprecation Notices
 * metrics: The function ``rte_metrics_init`` will have a non-void return
   in order to notify errors instead of calling ``rte_exit``.
-* power: ``rte_power_set_env`` function will no longer return 0 on attempt
-  to set new power environment if power environment was already initialized.
-  In this case the function will return -1 unless the environment is unset first
-  (using ``rte_power_unset_env``). Other function usage scenarios will not change.
 * cmdline: ``cmdline`` structure will be made opaque to hide platform-specific
   content. On Linux and FreeBSD, supported prior to DPDK 20.11,
   original structure will be kept until DPDK 21.11.

       reply	other threads:[~2020-10-27 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-10-27 13:24 ` David Hunt [this message]
2020-11-03 20:46   ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2020-11-04  9:28   ` [dpdk-stable] [PATCH v5] " David Hunt
2020-11-04 20:10     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).