From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: "Min Hu (Connor)" <humin29@huawei.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH v2] ethdev: fix dev close in secondary process
Date: Wed, 1 Jun 2022 06:45:26 -0700 [thread overview]
Message-ID: <CACZ4nhvZyjqL92V+MdbiNRZ0NWdQs-oGF_q5DC9mfJbtC1eEtw@mail.gmail.com> (raw)
In-Reply-To: <c816a78e-e900-4d26-05b1-f037ae3976da@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 123 bytes --]
On Tue, May 31, 2022 at 8:18 PM Min Hu (Connor) <humin29@huawei.com> wrote:
>
> Hi, Ajit
> v3 has been sent, thanks
Thanks
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
next prev parent reply other threads:[~2022-06-01 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 2:35 [PATCH] " Min Hu (Connor)
2022-05-31 17:08 ` Andrew Rybchenko
2022-05-31 17:40 ` Stephen Hemminger
2022-06-01 1:33 ` Min Hu (Connor)
2022-06-01 1:30 ` [PATCH v2] " Min Hu (Connor)
2022-06-01 2:01 ` Ajit Khaparde
2022-06-01 3:18 ` Min Hu (Connor)
2022-06-01 13:45 ` Ajit Khaparde [this message]
2022-06-01 3:15 ` [PATCH v3] " Min Hu (Connor)
2022-06-01 10:38 ` Andrew Rybchenko
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=CACZ4nhvZyjqL92V+MdbiNRZ0NWdQs-oGF_q5DC9mfJbtC1eEtw@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--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 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).