From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/6] net: ngbe PMD
Date: Fri, 2 Apr 2021 10:07:14 +0100 [thread overview]
Message-ID: <30034fde-0c79-ccc8-9399-0d0444b9c95c@intel.com> (raw)
In-Reply-To: <20210323022001.352-1-jiawenwu@trustnetic.com>
On 3/23/2021 2:19 AM, Jiawen Wu wrote:
> This patch set provides a skeleton of ngbe PMD,
> which adapted to Wangxun WX1860 series NICs.
>
> v3:
> - Use rte_ether functions to define marcos.
>
> v2:
> - Correct some clerical errors.
> - Use ethdev debug flags instead of driver own
>
> Jiawen Wu (6):
> net/ngbe: add build and doc infrastructure
> net/ngbe: add device IDs
> net/ngbe: support probe and remove
> net/ngbe: add device init and uninit
> net/ngbe: add log type and error type
> net/ngbe: define registers
>
Hi Jiawen,
I did not able to check the set yet, but the patch "net/ngbe: support probe and
remove" gives a build error, it looks like a struct used before it is declared.
Each patch should be compiled successfully, can you please send a new version
with fix.
prev parent reply other threads:[~2021-04-02 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 2:19 Jiawen Wu
2021-03-23 2:19 ` [dpdk-dev] [PATCH v3 1/6] net/ngbe: add build and doc infrastructure Jiawen Wu
2021-03-23 2:19 ` [dpdk-dev] [PATCH v3 2/6] net/ngbe: add device IDs Jiawen Wu
2021-03-23 2:19 ` [dpdk-dev] [PATCH v3 3/6] net/ngbe: support probe and remove Jiawen Wu
2021-03-23 2:19 ` [dpdk-dev] [PATCH v3 4/6] net/ngbe: add device init and uninit Jiawen Wu
2021-03-23 2:20 ` [dpdk-dev] [PATCH v3 5/6] net/ngbe: add log type and error type Jiawen Wu
2021-03-23 2:20 ` [dpdk-dev] [PATCH v3 6/6] net/ngbe: define registers Jiawen Wu
2021-03-29 10:07 ` [dpdk-dev] [PATCH v3 0/6] net: ngbe PMD Jiawen Wu
2021-04-02 9:07 ` 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=30034fde-0c79-ccc8-9399-0d0444b9c95c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jiawenwu@trustnetic.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).