From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH 0/8] make the logic conform the coding style of DPDK
Date: Fri, 19 May 2023 14:55:50 +0100 [thread overview]
Message-ID: <c5ca1e32-3831-ba3c-774e-1d8cbc0714e1@amd.com> (raw)
In-Reply-To: <20230519025950.1642943-1-chaoyong.he@corigine.com>
On 5/19/2023 3:59 AM, Chaoyong He wrote:
> Modify some logic of nfp PMD, to make it conform the coding style
> of DPDK.
>
> Also remove some unnecessary macro and functions which DPDK has
> already provided.
>
> Chaoyong He (8):
> net/nfp: reuse the ring buffer struct
> net/nfp: modify the rxq struct
> net/nfp: modify the Rx descriptor struct
> net/nfp: modify the txq struct
> net/nfp: remove the custom round macro
> net/nfp: remove the unneeded comment
> net/nfp: revise cast from void pointer
> net/nfp: revise the logic of MAC address
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-05-19 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 2:59 Chaoyong He
2023-05-19 2:59 ` [PATCH 1/8] net/nfp: reuse the ring buffer struct Chaoyong He
2023-05-19 2:59 ` [PATCH 2/8] net/nfp: modify the rxq struct Chaoyong He
2023-05-19 2:59 ` [PATCH 3/8] net/nfp: modify the Rx descriptor struct Chaoyong He
2023-05-19 2:59 ` [PATCH 4/8] net/nfp: modify the txq struct Chaoyong He
2023-05-19 2:59 ` [PATCH 5/8] net/nfp: remove the custom round macro Chaoyong He
2023-05-19 2:59 ` [PATCH 6/8] net/nfp: remove the unneeded comment Chaoyong He
2023-05-19 2:59 ` [PATCH 7/8] net/nfp: revise cast from void pointer Chaoyong He
2023-05-19 2:59 ` [PATCH 8/8] net/nfp: revise the logic of MAC address Chaoyong He
2023-05-19 13:55 ` 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=c5ca1e32-3831-ba3c-774e-1d8cbc0714e1@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).