From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>,
Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] doc: updated json sample code for fifo interface
Date: Mon, 13 May 2019 18:57:30 +0200 [thread overview]
Message-ID: <2693512.IeBxsWZDPR@xps> (raw)
Message-ID: <20190513165730.Cg-k9lMpTA4Qxcfc5f6Jgqr0AlSOgBA_2rmCXE-2pF0@z> (raw)
In-Reply-To: <20190513141355.8208-1-david.hunt@intel.com>
13/05/2019 16:13, David Hunt:
> From: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
>
> Updated doc for JSON sample code related to vm_power_manager
> fifo interface: "command": "destroy", "command": "power".
>
> There is no code change to go with this doc update, it is to fix
> the docs to match the implementation in the code.
>
> Fixes: a63504a90f ("examples/power: add JSON string handling")
> Cc: stable@dpdk.org
> Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
> Acked-by: David Hunt <david.hunt@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-13 16:57 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 ` [dpdk-dev] [PATCH v2] " Lukasz Krakowiak
2019-03-29 10:22 ` 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 [this message]
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=2693512.IeBxsWZDPR@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lukaszx.krakowiak@intel.com \
--cc=stable@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).