From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, helin.zhang@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] reduce writes in i40e driver
Date: Mon, 10 Apr 2017 14:13:10 +0100 [thread overview]
Message-ID: <4828c3d8-6fc7-16ab-f51d-534446d45282@intel.com> (raw)
In-Reply-To: <20170406113217.28236-1-bruce.richardson@intel.com>
On 4/6/2017 12:32 PM, Bruce Richardson wrote:
> this set is based upon Olivier's mbuf rework patchset, and makes some
> improvement to the i40e driver taking account of the rework. It also
> removes a build-time option that seems unnecessary.
>
> V2: Eliminate one checkpatch warning, and remove #ifdef block from
> new altivec driver code.
>
> Bruce Richardson (2):
> net/i40e: eliminate mbuf write on rearm
> net/i40e: remove option to disable offload flags
Acked-by: Jianbo Liu <jianbo.liu@linaro.org>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-04-10 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 14:39 [dpdk-dev] [PATCH " Bruce Richardson
2017-04-03 14:39 ` [dpdk-dev] [PATCH 1/2] net/i40e: eliminate mbuf write on rearm Bruce Richardson
2017-04-03 14:39 ` [dpdk-dev] [PATCH 2/2] net/i40e: remove option to disable offload flags Bruce Richardson
2017-04-03 14:45 ` Ferruh Yigit
2017-04-03 14:51 ` Bruce Richardson
2017-04-06 5:53 ` [dpdk-dev] [PATCH 0/2] reduce writes in i40e driver Jianbo Liu
2017-04-06 5:56 ` Jianbo Liu
2017-04-06 11:32 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2017-04-06 11:32 ` [dpdk-dev] [PATCH v2 1/2] net/i40e: eliminate mbuf write on rearm Bruce Richardson
2017-04-06 16:24 ` Zhang, Qi Z
2017-04-07 8:26 ` Bruce Richardson
2017-04-06 11:32 ` [dpdk-dev] [PATCH v2 2/2] net/i40e: remove option to disable offload flags Bruce Richardson
2017-04-10 13:13 ` 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=4828c3d8-6fc7-16ab-f51d-534446d45282@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@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).