From: Thomas Monjalon <thomas@monjalon.net>
To: "Min Hu (Connor)" <humin29@huawei.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/kni: add dev close step when kni free
Date: Wed, 06 Oct 2021 16:52:53 +0200 [thread overview]
Message-ID: <8737697.d4JhdggRFk@thomas> (raw)
In-Reply-To: <ba8fc7e1-40f0-f0dd-2310-32eb81b1b90b@intel.com>
21/09/2021 09:48, Ferruh Yigit:
> On 9/14/2021 7:02 AM, Min Hu (Connor) wrote:
> > From: Huisong Li <lihuisong@huawei.com>
> >
> > This patch adds dev_close() step to release network adapter resources
> > when kni free.
> >
> > Signed-off-by: Huisong Li <lihuisong@huawei.com>
> > Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Closing the port not directly related to the 'kni free', just both done before
> exiting the app, so I would update the patch title to something like:
> examples/kni: close port before exit
Applied, with suggested title, thanks.
prev parent reply other threads:[~2021-10-06 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 6:02 [dpdk-dev] [PATCH] examples/kni: add dev close step when kni free Min Hu (Connor)
2021-09-21 7:48 ` Ferruh Yigit
2021-10-06 14:52 ` 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=8737697.d4JhdggRFk@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.