From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/pdump: remove unused socket path options
Date: Thu, 26 Apr 2018 07:44:03 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A2C9FE0@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E3651533E07@SHSMSX103.ccr.corp.intel.com>
> -----Original Message-----
> From: Tan, Jianfeng
> Sent: Thursday, April 26, 2018 1:33 AM
> To: Thomas Monjalon <thomas@monjalon.net>; dev@dpdk.org
> Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; Pattan, Reshma
> <reshma.pattan@intel.com>
> Subject: RE: [PATCH] app/pdump: remove unused socket path options
>
>
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Wednesday, April 25, 2018 9:04 PM
> > To: dev@dpdk.org
> > Cc: Burakov, Anatoly; Pattan, Reshma; Tan, Jianfeng
> > Subject: [PATCH] app/pdump: remove unused socket path options
> >
> > The options --server-socket-path and --client-socket-path were said to
> > be deprecated and will be removed soon.
> > No need to wait for removing application options which have no effect,
> > and can confuse the user.
> >
> > Fixes: 660098d61f57 ("pdump: use generic multi-process channel")
> > Cc: jianfeng.tan@intel.com
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
Acked-by: Reshma Pattan <reshma.pattan@intel.com>
Thanks,
Reshma
next prev parent reply other threads:[~2018-04-26 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 13:03 Thomas Monjalon
2018-04-26 0:33 ` Tan, Jianfeng
2018-04-26 7:44 ` Pattan, Reshma [this message]
2018-04-26 16:20 ` 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=3AEA2BF9852C6F48A459DA490692831F2A2C9FE0@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=thomas@monjalon.net \
/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).