From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tiwei Bie <tiwei.bie@intel.com>, dev@dpdk.org
Cc: reshma.pattan@intel.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: update commands for pdump
Date: Thu, 22 Nov 2018 16:36:54 +0000 [thread overview]
Message-ID: <eed395c3-96a5-7028-ae4b-eba3f5bc4525@intel.com> (raw)
In-Reply-To: <20181122025138.31824-1-tiwei.bie@intel.com>
On 11/22/2018 2:51 AM, Tiwei Bie wrote:
> The --server-socket-path and --client-socket-path options
> have already been removed. So also remove them from the doc
> to avoid confusion.
>
> Fixes: 09f4aa2b955f ("app/pdump: remove unused socket path options")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-11-22 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 2:51 Tiwei Bie
2018-11-22 16:36 ` Ferruh Yigit [this message]
2018-11-22 17:54 ` Mcnamara, John
2018-11-25 9:57 ` [dpdk-dev] [dpdk-stable] " 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=eed395c3-96a5-7028-ae4b-eba3f5bc4525@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@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).