DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>, david.hunt@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: updated json sample code for fifo interface
Date: Thu, 09 May 2019 20:57:34 +0200	[thread overview]
Message-ID: <1658605.9gr7meREpW@xps> (raw)
Message-ID: <20190509185734.cwM_EQcGGeb1O7wqennP0tP1g5WCkKBFxa8dNPFOeU0@z> (raw)
In-Reply-To: <1892489.Zohctpogsv@xps>

23/04/2019 00:30, Thomas Monjalon:
> 29/03/2019 11:22, Lukasz Krakowiak:
> > 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>
> 
> The SoB must be above the ---
> Please add a line "Fixes:"

Why there is no update?



  parent reply	other threads:[~2019-05-09 18: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 [this message]
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=1658605.9gr7meREpW@xps \
    --to=thomas@monjalon.net \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=lukaszx.krakowiak@intel.com \
    /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).