DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
	"Archbold, Brian" <brian.archbold@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] app/testpmd: fix duplicate exit
Date: Thu, 11 Oct 2018 12:41:12 +0100	[thread overview]
Message-ID: <3980a41a-2daa-7655-e6e9-83fc07906c6e@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260CE8314@IRSMSX107.ger.corp.intel.com>

On 8/23/2018 12:16 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: Archbold, Brian
>> Sent: Wednesday, August 22, 2018 7:05 AM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
>> <jingjing.wu@intel.com>; Iremonger, Bernard <bernard.iremonger@intel.com>
>> Cc: dev@dpdk.org; Archbold, Brian <brian.archbold@intel.com>;
>> stable@dpdk.org
>> Subject: [PATCH] app/testpmd: fix duplicate exit
>>
>> In interactive mode, when the "quit" command is issued, pmd_test_exit() is
>> being called twice, once through the "quit" command and the other after
>> termination of prompt.
>>
>> Remove duplicated exit routine by removing call from "quit" command.
>>
>> Steps to reproduce:
>> - Run testpmd in interactive mode.
>> - type "quit".
>>
>> Fixes: af75078fece3 ("first public release")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Brian Archbold <brian.archbold@intel.com>
> 
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2018-10-11 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22  6:05 [dpdk-dev] " Brian Archbold
2018-08-23 11:16 ` Iremonger, Bernard
2018-10-11 11:41   ` Ferruh Yigit [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=3980a41a-2daa-7655-e6e9-83fc07906c6e@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=brian.archbold@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@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).