From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7A4A345E30 for ; Wed, 4 Dec 2024 13:00:03 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0B4F440B92; Wed, 4 Dec 2024 13:00:03 +0100 (CET) Received: from fout-a5-smtp.messagingengine.com (fout-a5-smtp.messagingengine.com [103.168.172.148]) by mails.dpdk.org (Postfix) with ESMTP id CDC0740B92 for ; Wed, 4 Dec 2024 13:00:00 +0100 (CET) Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id 475371380B57; Wed, 4 Dec 2024 07:00:00 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-02.internal (MEProxy); Wed, 04 Dec 2024 07:00:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1733313600; x=1733400000; bh=s3GaVyHP0YV3Io+H9uU9oIwS/B1V/6sX69u/FX1G3OU=; b= a8ChvM6NnkP86gPMLXeQl7zsiU67r2M14CULvDYqQbAyMOT1mlwQvnIDtSJpnF+i ublw+yQzHiybrljIkijHrIcW+P5epmICi7HptrADcWEsLl0zVrgg5vM+i7XlCdb+ gJmabr3txnBRakm7az+0R9dGKWY64vrG5cZGQlXONYe40yE9Z9g//7PPetAdRDBv eUY4Oa0GJbrlLIIWLc2mP9D3b0U2qJ5/vUINWGGAvrQCUH9oMEPnUctRmrKjLMdT 8sRKb5aniOpY1w/yfWiYjZGsrScVZcrIAkAAv1Pf43NGq5PBDGPrmt535RGXNGqb k1HaTBDNTBMjLoKx0l7+8w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1733313600; x= 1733400000; bh=s3GaVyHP0YV3Io+H9uU9oIwS/B1V/6sX69u/FX1G3OU=; b=K 2e6B0THGC4eGW3HnA8Dw4cfIHlzzUkZutvod8fepcoshaQkliVA88l5AzbsUSSX3 WilN4qAwu+wsI7FelZbKATm3PIPn8kOH7fCsM3OsMaVN3RhLAcDeY79BXmnYavRH UcWRhwj+PsAP3IMNll/7rWvf5hRJJAQp519kSiAvtlWFrPQcCfDlkIZbNqpEEolc 1S3aDot2v6/aS28SZB74JX8T+uGHBef9lUeTL5UKDSbeySjX8uhoQ5sF72z9sspM OU0chkNPQQXvAN9ZopnPPGyOYpL4csF7vk+osb/pqdF7TltGITj4+EuSlEEy0bj0 +jbnrYMp82VyuyTD+pe0w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrieehgdefudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvvefuff fkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhho nhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpe fftdeuhfehvdekleelveffvdelhfelhedvgedtvddvudeuieevtdfgjedvudegfeenucff ohhmrghinhepughpughkrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthdpnhgspghr tghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepiihhrghnghhtrg hohihmseduvdeirdgtohhmpdhrtghpthhtohepuhhsvghrshesughpughkrdhorhhg X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 Dec 2024 06:59:59 -0500 (EST) From: Thomas Monjalon To: =?UTF-8?B?5byg54SY?= 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 Message-ID: <9245238.EvYhyI6sBW@thomas> In-Reply-To: <6b5794ca.9204.1938be9376b.Coremail.zhangtaoym@126.com> References: <6b5794ca.9204.1938be9376b.Coremail.zhangtaoym@126.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hello, 03/12/2024 10:45, =E5=BC=A0=E7=84=98: > 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 relea= se version? You can follow this guide: https://doc.dpdk.org/guides/contributing/new_driver.html