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 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 submit > +the driver until the dependent library is available. > + Could you please interpret dependencies publicly and freely？There are 4 scenarios as below: 1. A dependency is niche software, but it's open-sourced on github, is it publicly or freely? 2. A dependency which belongs to our company and open-sourced on github, is it publicly or freely? 3. A dependency which is not available in the upstream distribution, but available in the downstream distribution. For instance, a kernel driver dependent upon by PMD, which is not available in kernel.org，but it's available in openeuler kernel, the openeuler kernel is publicly and freely. Is it publicly or freely?4. If a distribution does not include the dependency, I redistribute it with the dependency and open source, 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 questions above, could you please explain them? Thank you. -- Thanks, WanRenyong
