From: Thomas Monjalon <thomas@monjalon.net>
To: Matan Azrad <matan@mellanox.com>
Cc: dev@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] app/testpmd: fix invalid port detach
Date: Wed, 31 Jan 2018 21:36:55 +0100 [thread overview]
Message-ID: <3030595.E4uSP6LIab@xps> (raw)
In-Reply-To: <1517321620-14198-2-git-send-email-matan@mellanox.com>
30/01/2018 15:13, Matan Azrad:
> Using registration to all ports includes also the ports which should not
> be used by the application.
>
> It is nice to print each port event by testpmd but in case of RMV
> event, testpmd tries to detach the port and this case is problematic
> when the port should not be used by the application.
>
> Check the port validation before detach API calling.
>
> Fixes: 4fb82244b394 ("app/testpmd: extend event printing")
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
Series applied, thanks
prev parent reply other threads:[~2018-01-31 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 14:13 [dpdk-dev] [PATCH 1/2] app/testpmd: fix port validation Matan Azrad
2018-01-30 14:13 ` [dpdk-dev] [PATCH 2/2] app/testpmd: fix invalid port detach Matan Azrad
2018-01-31 20:36 ` 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=3030595.E4uSP6LIab@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--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).