From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
wenzhuo.lu@intel.com, qiming.yang@intel.com
Cc: paul.m.stillwell.jr@intel.com, dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/7] net/ice: update share code
Date: Wed, 16 Jan 2019 12:16:36 +0000 [thread overview]
Message-ID: <a1cdee33-25ed-6947-dc72-ea01f89c14a3@intel.com> (raw)
In-Reply-To: <20190115125658.15421-1-qi.z.zhang@intel.com>
On 1/15/2019 12:56 PM, Qi Zhang wrote:
> For ice family NICs, package processing pipe line can be configured in
> a package file should be downloaded into device by driver during init.
> The patch set add necessary share code APIs to support package download.
> Also some code clean is included.
>
> Though package download will not be enabled in 19.02 as plan, but we
> hope the share code part could be merged early.
>
> Meanwhile we will submit a seperate RFC patch for package download for
> customer early evelutation.
>
> Qi Zhang (7):
> net/ice/base: code clean
> net/ice/base: add API to support resource allocate
> net/ice/base: add package download related data structure
> net/ice/base: add some help macros
> net/ice/base: add flexible pipeline module
> net/ice/base: add flow module
> net/ice/base: free flow profile entries
Since there will be already a new version, can you also check the checkpatch
errors, there are a few reported.
Thanks,
ferruh
next prev parent reply other threads:[~2019-01-16 12:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 12:56 Qi Zhang
2019-01-15 12:56 ` [dpdk-dev] [PATCH 1/7] net/ice/base: code clean Qi Zhang
2019-01-15 12:56 ` [dpdk-dev] [PATCH 2/7] net/ice/base: add API to support resource allocate Qi Zhang
2019-01-15 12:56 ` [dpdk-dev] [PATCH 3/7] net/ice/base: add package download related data structure Qi Zhang
2019-01-15 12:56 ` [dpdk-dev] [PATCH 4/7] net/ice/base: add some help macros Qi Zhang
2019-01-15 12:56 ` [dpdk-dev] [PATCH 5/7] net/ice/base: add flexible pipeline module Qi Zhang
2019-01-15 12:56 ` [dpdk-dev] [PATCH 6/7] net/ice/base: add flow module Qi Zhang
2019-01-16 12:14 ` Ferruh Yigit
2019-01-15 12:56 ` [dpdk-dev] [PATCH 7/7] net/ice/base: free flow profile entries Qi Zhang
2019-01-16 12:15 ` Ferruh Yigit
2019-01-16 5:05 ` [dpdk-dev] [PATCH 0/7] net/ice: update share code Lu, Wenzhuo
2019-01-16 12:16 ` Ferruh Yigit [this message]
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 " Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 1/7] net/ice/base: code clean Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 2/7] net/ice/base: add API to support resource allocate Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 3/7] net/ice/base: add package download related data structure Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 4/7] net/ice/base: add some help macros Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 5/7] net/ice/base: add flexible pipeline module Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 6/7] net/ice/base: add flow module Qi Zhang
2019-01-16 14:13 ` [dpdk-dev] [PATCH v2 7/7] net/ice/base: free flow profile entries Qi Zhang
2019-01-17 13:31 ` [dpdk-dev] [PATCH v2 0/7] net/ice: update share code 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=a1cdee33-25ed-6947-dc72-ea01f89c14a3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=paul.m.stillwell.jr@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=wenzhuo.lu@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).