From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Michal Krawczyk <mk@semihalf.com>, dev@dpdk.org
Cc: mw@semihalf.com, igorch@amazon.com, gtzalik@amazon.com
Subject: Re: [dpdk-dev] [PATCH 0/6] net/ena: fixes and missing version/doc udate
Date: Fri, 30 Oct 2020 23:48:25 +0000 [thread overview]
Message-ID: <e15b9fc1-f8a0-fc48-d8c1-75e406dd4962@intel.com> (raw)
In-Reply-To: <20201030113121.1310305-1-mk@semihalf.com>
On 10/30/2020 11:31 AM, Michal Krawczyk wrote:
> Hi,
>
> This patchset contains few fixes, and two of them are very important:
> * Fix for setting Rx checksum flags
> * align IO cq allocation to 4k
>
> Also it adds missing release notes regarding the ENI metrics which
> should go with the patches upstreamed previously, and also increases
> the driver version to v2.2.0
>
> Michal Krawczyk (6):
> net/ena: fix getting xstats global stats offset
> net/ena: fix setting Rx checksum flags in mbuf
> net/ena: change name of the supported PCI device IDs
> net/ena/base: align IO cq allocation to a 4K
> doc: mark ARMv8 as supported by ENA PMD
> net/ena: upgrade driver version to v2.2.0
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-30 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 11:31 Michal Krawczyk
2020-10-30 11:31 ` [dpdk-dev] [PATCH 1/6] net/ena: fix getting xstats global stats offset Michal Krawczyk
2020-10-30 11:31 ` [dpdk-dev] [PATCH 2/6] net/ena: fix setting Rx checksum flags in mbuf Michal Krawczyk
2020-10-30 11:31 ` [dpdk-dev] [PATCH 3/6] net/ena: change name of the supported PCI device IDs Michal Krawczyk
2020-10-30 11:31 ` [dpdk-dev] [PATCH 4/6] net/ena/base: align IO cq allocation to a 4K Michal Krawczyk
2020-10-30 11:31 ` [dpdk-dev] [PATCH 5/6] doc: mark ARMv8 as supported by ENA PMD Michal Krawczyk
2020-10-30 11:31 ` [dpdk-dev] [PATCH 6/6] net/ena: upgrade driver version to v2.2.0 Michal Krawczyk
2020-10-30 23:48 ` Ferruh Yigit [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=e15b9fc1-f8a0-fc48-d8c1-75e406dd4962@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.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).