DPDK usage discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: 张焘 <zhangtaoym@126.com>
Cc: users@dpdk.org
Subject: Re: How can I upload my self-developed DPDK driver to the standard DPDK release version?
Date: Wed, 04 Dec 2024 12:59:57 +0100	[thread overview]
Message-ID: <9245238.EvYhyI6sBW@thomas> (raw)
In-Reply-To: <6b5794ca.9204.1938be9376b.Coremail.zhangtaoym@126.com>

Hello,

03/12/2024 10:45, 张焘:
> Dear mr/ms,
> I developed my own network card and support DPDK functionality.

Is your network card distributed publicly?
We need this kind of information to decide whether we want to maintain this driver.

> How can I upload my self-developed DPDK driver to the standard DPDK release version?

You can follow this guide:
	https://doc.dpdk.org/guides/contributing/new_driver.html



      parent reply	other threads:[~2024-12-04 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  9:45 张焘
2024-12-04 10:07 ` Lukáš Šišmiš
2024-12-04 11:59 ` Thomas Monjalon [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=9245238.EvYhyI6sBW@thomas \
    --to=thomas@monjalon.net \
    --cc=users@dpdk.org \
    --cc=zhangtaoym@126.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).