DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
To: david.hunt@intel.com
Cc: dev@dpdk.org, Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: updated json sample code for fifo interface
Date: Fri, 29 Mar 2019 11:22:19 +0100	[thread overview]
Message-ID: <20190329102219.17876-1-lukaszx.krakowiak@intel.com> (raw)
Message-ID: <20190329102219.d3V9mYt5AJgIOwzuCt8Yi1-pbu3o3QOa4JfXEoFD6g8@z> (raw)
In-Reply-To: <20190329101104.18360-1-lukaszx.krakowiak@intel.com>

Updated doc for JSON sample code related to vm_power_manager
fifo interface: "command": "destroy", "command": "power".
Corrected typo in doc vm_power_management.rst: 'json' instead
of 'jason'.

---
v2:
* coding style improved

Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
---
 doc/guides/sample_app_ug/vm_power_management.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 14d432e78..0182a92b3 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -384,7 +384,7 @@ the file.
 
 The fifo is at /tmp/powermonitor/fifo
 
-The jason string can be a policy or instruction, and takes the following
+The json string can be a policy or instruction, and takes the following
 format:
 
   .. code-block:: javascript
@@ -597,7 +597,7 @@ Profile destroy example:
 
   .. code-block:: javascript
 
-    {"profile": {
+    {"policy": {
       "name": "ubuntu",
       "command": "destroy",
     }}
@@ -606,8 +606,9 @@ Power command example:
 
   .. code-block:: javascript
 
-    {"command": {
+    {"instruction": {
       "name": "ubuntu",
+      "command": "power",
       "unit": "SCALE_MAX",
       "resource_id": 10
     }}
-- 
2.19.2.windows.1


  parent reply	other threads:[~2019-03-29 10:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 10:11 [dpdk-dev] [PATCH] " Lukasz Krakowiak
2019-03-29 10:11 ` Lukasz Krakowiak
2019-03-29 10:22 ` Lukasz Krakowiak [this message]
2019-03-29 10:22   ` [dpdk-dev] [PATCH v2] " Lukasz Krakowiak
2019-04-15 15:06   ` Hunt, David
2019-04-15 15:06     ` Hunt, David
2019-04-22 22:30   ` Thomas Monjalon
2019-04-22 22:30     ` Thomas Monjalon
2019-05-09 18:57     ` Thomas Monjalon
2019-05-09 18:57       ` Thomas Monjalon
2019-05-13  9:04   ` [dpdk-dev] [PATCH v3] " David Hunt
2019-05-13  9:04     ` David Hunt
2019-05-13 13:49     ` Thomas Monjalon
2019-05-13 13:49       ` Thomas Monjalon
2019-05-13 14:13     ` [dpdk-dev] [PATCH v4] " David Hunt
2019-05-13 14:13       ` David Hunt
2019-05-13 16:57       ` Thomas Monjalon
2019-05-13 16:57         ` 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=20190329102219.17876-1-lukaszx.krakowiak@intel.com \
    --to=lukaszx.krakowiak@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).