From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>, beilei.xing@intel.com
Cc: ting.xu@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] common/iavf: update version
Date: Thu, 15 Oct 2020 22:06:29 +0100 [thread overview]
Message-ID: <8e1e7ca7-efdc-a96a-4b3f-5767185f2c07@intel.com> (raw)
In-Reply-To: <20201015004325.1016100-4-qi.z.zhang@intel.com>
On 10/15/2020 1:43 AM, Qi Zhang wrote:
> Update base code release version in readme
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
> drivers/common/iavf/README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/common/iavf/README b/drivers/common/iavf/README
> index f301ff665a..5a42750465 100644
> --- a/drivers/common/iavf/README
> +++ b/drivers/common/iavf/README
> @@ -6,7 +6,7 @@ Intel® IAVF driver
> =================
>
> This directory contains source code of FreeBSD IAVF driver of version
> -cid-avf.2020.04.09.tar.gz released by the team which develops
> +cid-avf.2020.10.14.tar.gz released by the team which develops
> basic drivers for any IAVF NIC. The directory of base/ contains the
> original source package.
>
>
Since previous patch seems the main update for this drop and there is no more
patches, so may not need a separate patch to update version, what do you think
merging this patch with previous one?
next prev parent reply other threads:[~2020-10-15 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 0:43 [dpdk-dev] [PATCH 0/3] iavf update base code Qi Zhang
2020-10-15 0:43 ` [dpdk-dev] [PATCH 1/3] common/iavf: replace macro for MAC address length Qi Zhang
2020-10-15 21:04 ` Ferruh Yigit
2020-10-15 0:43 ` [dpdk-dev] [PATCH 2/3] common/iavf: add support for VFs with >16 queue pairs Qi Zhang
2020-10-15 0:43 ` [dpdk-dev] [PATCH 3/3] common/iavf: update version Qi Zhang
2020-10-15 21:06 ` Ferruh Yigit [this message]
2020-10-15 8:42 ` [dpdk-dev] [PATCH 0/3] iavf update base code Xing, Beilei
2020-10-15 15:28 ` Zhang, Qi Z
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=8e1e7ca7-efdc-a96a-4b3f-5767185f2c07@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=ting.xu@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).