DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>
Cc: dev@dpdk.org, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] add new command line options and error	handling in pdump
Date: Sat, 16 Jul 2016 11:15:12 +0200	[thread overview]
Message-ID: <2574033.PAqWrXVS0T@xps13> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836B7DD09@irsmsx105.ger.corp.intel.com>

2016-07-14 09:59, Ananyev, Konstantin:
> 
> This patch set contains
> 1)Error handling fixes in pdump library.
> 2)Support of server and client socket path command line options in pdump tool.
> 3)Default socket path name fixes in pdump library doc.
> 
> Reshma Pattan (3):
>   pdump: fix error handlings
>   app/pdump: add new command line options for socket paths
>   doc: fix default socket path names
> 
>  app/pdump/main.c                    | 57 +++++++++++++++++++++++++++++++------
>  doc/guides/prog_guide/pdump_lib.rst | 12 ++++----  doc/guides/sample_app_ug/pdump.rst  | 31 ++++++++++++++------
>  lib/librte_pdump/rte_pdump.c        | 26 +++++++++++++----
>  4 files changed, 97 insertions(+), 29 deletions(-)
> 
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

Applied, thanks

      reply	other threads:[~2016-07-16  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 16:29 Reshma Pattan
2016-07-13 16:29 ` [dpdk-dev] [PATCH 1/3] pdump: fix error handlings Reshma Pattan
2016-07-13 16:29 ` [dpdk-dev] [PATCH 2/3] app/pdump: add new command line options for socket paths Reshma Pattan
2016-07-13 16:29 ` [dpdk-dev] [PATCH 3/3] doc: fix default socket path names Reshma Pattan
2016-07-14  9:59 ` [dpdk-dev] [PATCH 0/3] add new command line options and error handling in pdump Ananyev, Konstantin
2016-07-16  9:15   ` Thomas Monjalon [this message]

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=2574033.PAqWrXVS0T@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=reshma.pattan@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).