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 0280345975; Fri, 13 Sep 2024 06:20:09 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 81B8F402C8; Fri, 13 Sep 2024 06:20:09 +0200 (CEST) Received: from lf-1-33.ptr.blmpb.com (lf-1-33.ptr.blmpb.com [103.149.242.33]) by mails.dpdk.org (Postfix) with ESMTP id B70374025E for ; Fri, 13 Sep 2024 06:20:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=feishu2403070942; d=yunsilicon.com; t=1726201201; h=from:subject: mime-version:from:date:message-id:subject:to:cc:reply-to:content-type: mime-version:in-reply-to:message-id; bh=Qtn8+Zxgcf7CtaoSRnOtOSFuMVzqPaWbKApeWJyB2p0=; b=BVMx+hrnBd3k66QGmGNV9rWBi4K/JvXtZS+rqz24Qm674t5s6wyweW3TECRKNN50mNB2s4 EyYyUF9lkEnI4byBwAXxk6r3gRuJlHAlvwdqIEPCBz1jjCHNV+ec+JGWyGZYIuDC8CV0W0 gqb3hiO3jVRxDit2+64XV3vFHHNYBdsJkPXxQ5HaICzO3fOG8T3s6BNZhMdW71ZJB9Zq6L ArF7CS7e9kthSSCSa8FxCe/5w/SYLd9nHjmANrVM7ofCGinMc5UkWfw0A3cimTPfydoEgZ qrEL4oYWNOYaztIaf7U0kfB0wBpH22xRNaooTcLwuHUXK27WicYa0rUMVOfOog== Date: Fri, 13 Sep 2024 12:19:59 +0800 Mime-Version: 1.0 References: <20240814190901.14912-1-stephen@networkplumber.org> <20240912202734.24440-1-stephen@networkplumber.org> X-Lms-Return-Path: User-Agent: Mozilla Thunderbird Cc: "Nandini Persad" , "Ferruh Yigit" , "Thomas Monjalon" Content-Transfer-Encoding: quoted-printable In-Reply-To: <20240912202734.24440-1-stephen@networkplumber.org> X-Original-From: WanRenyong From: "WanRenyong" Message-Id: Content-Type: text/plain; charset=UTF-8 To: "Stephen Hemminger" , Received: from [127.0.0.1] ([222.64.242.227]) by smtp.feishu.cn with ESMTPS; Fri, 13 Sep 2024 12:20:00 +0800 Subject: Re: [PATCH v3] doc: add new driver guidelines X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On 2024/9/13 4:26, Stephen Hemminger wrote > + > +Finalizing > +---------- > + > +Once the driver has been upstreamed, the author has > +a responsibility to the community to maintain it. > + > +This includes the public test report. Authors must send a public > +test report after the first upstreaming of the PMD. The same > +public test procedure may be reproduced regularly per release. Is there any guildelines about how to write a test report? Is there any=20 template? > + > +Dependencies > +------------ > + > +At times, drivers may have dependencies to external software. > +For driver dependencies, same DPDK rules for dependencies applies. > +Dependencies should be publicly and freely available, > +drivers which depend on non-available components will not be accepted. > +If the required dependency is not yet publicly available, then wait to s= ubmit > +the driver until the dependent library is available. > + Could you please interpret dependencies publicly and freely=EF=BC=9FThere a= re 4=20 scenarios as below: 1. A dependency is niche software, but it's open-sourced on github, is=20 it publicly or freely? 2. A dependency which belongs to our company and open-sourced on github,=20 is it publicly or freely? 3. A dependency which is not available in the upstream distribution, but=20 available in the downstream distribution. For instance, a kernel driver=20 dependent upon by PMD, which is not available in kernel.org=EF=BC=8Cbut it'= s=20 available in openeuler kernel, the openeuler kernel is publicly and=20 freely.=C2=A0 Is it publicly or freely?4. If a distribution does not includ= e=20 the dependency, I redistribute it with the dependency and open source,=20 this is somewhat similar to mlnx_ofed, is it publicly or freely? Hello, Stephen, These guildelines are very useful for begineers like me :). I have some=20 questions above, could you please explain them? Thank you. --=20 Thanks, WanRenyong