DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: liwencheng <liwencheng@phytium.com.cn>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1] net/macb: add new driver
Date: Wed, 30 Oct 2024 10:14:13 +0000	[thread overview]
Message-ID: <ZyIG9c5FKnviyWD4@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1730282009-562817-1-git-send-email-liwencheng@phytium.com.cn>

On Wed, Oct 30, 2024 at 09:53:29AM +0000, liwencheng wrote:
> add Phytium NIC MACB ethdev PMD driver.
> 
> Signed-off-by: liwencheng <liwencheng@phytium.com.cn>
> ---
>  drivers/net/macb/base/generic_phy.c   |  276 +++++
>  drivers/net/macb/base/generic_phy.h   |  198 ++++
>  drivers/net/macb/base/macb_common.c   |  667 +++++++++++
>  drivers/net/macb/base/macb_common.h   |  253 +++++
>  drivers/net/macb/base/macb_errno.h    |   54 +
>  drivers/net/macb/base/macb_hw.h       | 1138 +++++++++++++++++++
>  drivers/net/macb/base/macb_type.h     |   23 +
>  drivers/net/macb/base/macb_uio.c      |  354 ++++++
>  drivers/net/macb/base/macb_uio.h      |   50 +
>  drivers/net/macb/base/meson.build     |   26 +
>  drivers/net/macb/macb_ethdev.c        | 1972 +++++++++++++++++++++++++++++++++
>  drivers/net/macb/macb_ethdev.h        |   92 ++
>  drivers/net/macb/macb_log.h           |   19 +
>  drivers/net/macb/macb_rxtx.c          | 1386 +++++++++++++++++++++++
>  drivers/net/macb/macb_rxtx.h          |  325 ++++++
>  drivers/net/macb/macb_rxtx_vec_neon.c |  677 +++++++++++
>  drivers/net/macb/meson.build          |   18 +
>  drivers/net/meson.build               |    1 +
>  usertools/dpdk-devbind.py             |   95 +-
>  19 files changed, 7622 insertions(+), 2 deletions(-)

Hi,

thanks for the contribution. However, in order to aid reviewing and merging
of new drivers, the policy in DPDK is that the driver be split into logically
distinct patches, rather than a single massive patch. For contributing
guidelines see [1], and especially see the section on new drivers [2], and
the subsection within that on patch splitting [3].

Thanks,
/Bruce

[1] https://doc.dpdk.org/guides/contributing/index.html
[2] https://doc.dpdk.org/guides/contributing/new_driver.html
[3] https://doc.dpdk.org/guides/contributing/new_driver.html#splitting-into-patches

  reply	other threads:[~2024-10-30 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30  9:53 liwencheng
2024-10-30 10:14 ` Bruce Richardson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-30  7:59 liwencheng
2024-10-30  5:51 liwencheng

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=ZyIG9c5FKnviyWD4@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=liwencheng@phytium.com.cn \
    /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).