DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jakub Palider <jpalider@gmail.com>, Marcin Wojtas <mw@semihalf.com>
Cc: dev@dpdk.org, "Jan Mędala" <jan.medala@outlook.com>,
	netanel@amazon.com, evgenys@amazon.com, matua@amazon.com,
	gtzalik@amazon.com, igorch@amazon.com, mk@semihalf.com
Subject: Re: [dpdk-dev] [PATCH v2 0/4] Ena PMD fixes
Date: Wed, 12 Apr 2017 12:22:22 +0100	[thread overview]
Message-ID: <6673d9c2-b350-32d8-45dc-a19826561a06@intel.com> (raw)
In-Reply-To: <CAO-cEe=UtYoA=9PxtByeaLV_KyfhoQCQ6f2kqCs7BWZ_om06yQ@mail.gmail.com>

On 4/10/2017 11:20 PM, Jakub Palider wrote:
> On Mon, Apr 10, 2017 at 4:28 PM, Marcin Wojtas <mw@semihalf.com> wrote:

<...>
>> Michal Krawczyk (4):
>>   net/ena: fix incorrect Rx descriptors allocation
>>   net/ena: fix delayed cleanup of Rx descriptors
>>   net/ena: cleanup if refilling of rx descriptors fails
>>   net/ena: calculate partial checksum if DF bit is disabled

> ​Reviewed-by: Jakub Palider <jpalider@gmail.com>

Acked-by: Jan Medala <jan.medala@outlook.com>

Series applied to dpdk-next-net/master, thanks.

  reply	other threads:[~2017-04-12 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 14:28 Marcin Wojtas
2017-04-10 14:28 ` [dpdk-dev] [PATCH v2 1/4] net/ena: fix incorrect Rx descriptors allocation Marcin Wojtas
2017-04-10 14:28 ` [dpdk-dev] [PATCH v2 2/4] net/ena: fix delayed cleanup of Rx descriptors Marcin Wojtas
2017-04-10 14:28 ` [dpdk-dev] [PATCH v2 3/4] net/ena: cleanup if refilling of rx descriptors fails Marcin Wojtas
2017-04-10 14:28 ` [dpdk-dev] [PATCH v2 4/4] net/ena: calculate partial checksum if DF bit is disabled Marcin Wojtas
2017-04-10 22:20 ` [dpdk-dev] [PATCH v2 0/4] Ena PMD fixes Jakub Palider
2017-04-12 11:22   ` Ferruh Yigit [this message]
2017-04-11  8:29 ` Jan M?dala

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=6673d9c2-b350-32d8-45dc-a19826561a06@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=evgenys@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=igorch@amazon.com \
    --cc=jan.medala@outlook.com \
    --cc=jpalider@gmail.com \
    --cc=matua@amazon.com \
    --cc=mk@semihalf.com \
    --cc=mw@semihalf.com \
    --cc=netanel@amazon.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).