From: Bruce Richardson <bruce.richardson@intel.com>
To: "Hore, Soumyadeep" <soumyadeep.hore@intel.com>
Cc: "Singh, Aman Deep" <aman.deep.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wani, Shaiq" <shaiq.wani@intel.com>
Subject: Re: [PATCH v1] common/iavf: update README documentation
Date: Tue, 17 Sep 2024 15:23:43 +0100 [thread overview]
Message-ID: <ZumQ7wVhcEHio5Ie@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CY8PR11MB7747E7A73558C06FDE3E8773F9612@CY8PR11MB7747.namprd11.prod.outlook.com>
On Tue, Sep 17, 2024 at 03:20:59PM +0100, Hore, Soumyadeep wrote:
> Hi Bruce,
>
> The below wording looks fine. We can proceed with it.
>
Applied to dpdk-next-net-intel after base code update patchset.
Thanks,
/Bruce
prev parent reply other threads:[~2024-09-17 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 11:45 Soumyadeep Hore
2024-09-17 13:40 ` Bruce Richardson
2024-09-17 14:20 ` Hore, Soumyadeep
2024-09-17 14:23 ` Bruce Richardson [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=ZumQ7wVhcEHio5Ie@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=shaiq.wani@intel.com \
--cc=soumyadeep.hore@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).