From: Thomas Monjalon <thomas@monjalon.net>
To: Eduard Serra <eserra@vmware.com>
Cc: dev@dpdk.org, eduser25@gmail.com, yongwang@vmware.com
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitions with 6.7 public
Date: Thu, 04 Apr 2019 23:26:52 +0200 [thread overview]
Message-ID: <1760571.o9aQio58az@xps> (raw)
Message-ID: <20190404212652.jlmU2Mwex1BtKwgkGKlRfjWIYIn5lD_R6answiMKAJY@z> (raw)
In-Reply-To: <1554411251-67227-1-git-send-email-eserra@vmware.com>
Hi,
> From: Eduard Serra <eserra@vmware.com>
>
> Synchronize new definitions made public defs on ESX 6.7, which
> include support for variety of new features and fixes on vmxnet3
> driver.
Please, would it be possible to split this patch,
and add explanations in each patch for each feature or cleanup?
Thank you
next prev parent reply other threads:[~2019-04-04 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 20:54 eduser25
2019-04-04 20:54 ` eduser25
2019-04-04 21:26 ` Thomas Monjalon [this message]
2019-04-04 21:26 ` Thomas Monjalon
2019-04-07 0:36 ` [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitionswith " Eduard Serra
2019-04-07 0:36 ` Eduard Serra
2019-04-07 9:16 ` Thomas Monjalon
2019-04-07 9:16 ` Thomas Monjalon
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=1760571.o9aQio58az@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=eduser25@gmail.com \
--cc=eserra@vmware.com \
--cc=yongwang@vmware.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).