From: me thi <methi@gmx.fr>
To: "Yigit, Ferruh" <Ferruh.Yigit@amd.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: RE: DPDK and wifi
Date: Thu, 19 May 2022 15:28:37 +0200 [thread overview]
Message-ID: <trinity-66add5fb-fb18-4d80-8271-8474c03ea013-1652966917665@3c-app-mailcom-bs08> (raw)
In-Reply-To: <CH2PR12MB429424414AF1548909DFF8C687D09@CH2PR12MB4294.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/html, Size: 5086 bytes --]
prev parent reply other threads:[~2022-05-19 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:26 me thi
2022-05-19 12:49 ` Yigit, Ferruh
2022-05-19 13:07 ` Kinsella, Ray
2022-05-19 13:31 ` me thi
2022-05-19 15:29 ` Stephen Hemminger
2022-05-23 8:07 ` me thi
2022-05-19 13:28 ` me thi [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=trinity-66add5fb-fb18-4d80-8271-8474c03ea013-1652966917665@3c-app-mailcom-bs08 \
--to=methi@gmx.fr \
--cc=Ferruh.Yigit@amd.com \
--cc=hemant.agrawal@nxp.com \
--cc=users@dpdk.org \
/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).