DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Vlad Zolotarov <vladz@cloudius-systems.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/3]: bug fixes in the ixgbe PF PMD Rx flow
Date: Mon, 16 Mar 2015 11:19:30 +0100	[thread overview]
Message-ID: <18770784.9D0jN7h6Re@xps13> (raw)
In-Reply-To: <55068BD5.9090000@cloudius-systems.com>

Hi Vlad,

2015-03-16 09:52, Vlad Zolotarov:
> On 03/13/15 15:03, Vladislav Zolotarov wrote:
> > Thomas, it seems like ixgbe maintainer gives this series a green 
> > light!.. ;)
> 
> Ping.
> Thomas, could u, pls., consider  applying this series to at least the 
> upstream master?

Yes, of course.
Just a note: I didn't merge it during my week-end and I think it is not
needed to ping only one day after.
Traffic on the list is becoming high; let's focus on important messages.

  reply	other threads:[~2015-03-16 10:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 21:17 Vlad Zolotarov
2015-03-12 21:17 ` [dpdk-dev] [PATCH v3 1/3] ixgbe: Use the rte_le_to_cpu_xx()/rte_cpu_to_le_xx() when reading/setting HW ring descriptor fields Vlad Zolotarov
2015-03-12 21:17 ` [dpdk-dev] [PATCH v3 2/3] ixgbe: Bug fix: Properly configure Rx CRC stripping for x540 devices Vlad Zolotarov
2015-03-12 21:17 ` [dpdk-dev] [PATCH v3 3/3] ixgbe: Unify the rx_pkt_bulk callback initialization Vlad Zolotarov
2015-03-13 11:07 ` [dpdk-dev] [PATCH v3 0/3]: bug fixes in the ixgbe PF PMD Rx flow Ananyev, Konstantin
2015-03-13 11:51   ` Vlad Zolotarov
2015-03-13 12:51     ` Ananyev, Konstantin
2015-03-13 13:03       ` Vladislav Zolotarov
2015-03-16  7:52         ` Vlad Zolotarov
2015-03-16 10:19           ` Thomas Monjalon [this message]
2015-03-16 23: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=18770784.9D0jN7h6Re@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=vladz@cloudius-systems.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).