24/05/2022 19:44, David Marchand:
> On Tue, May 24, 2022 at 7:21 PM Thomas Monjalon wrote:
> > 23/05/2022 09:10, David Marchand:
> > > +# Driver specific sources include some testpmd headers.
> >
> > Suggested reword:
> > Driver-specific commands are located in driver directories.
>
> At
On Tue, May 24, 2022 at 7:21 PM Thomas Monjalon wrote:
>
> 23/05/2022 09:10, David Marchand:
> > Introduce a testpmd API so that drivers can register specific commands.
> >
> > A driver can list some files to compile with testpmd, by setting them
> > in the testpmd_sources (driver local) meson var
23/05/2022 09:10, David Marchand:
> Introduce a testpmd API so that drivers can register specific commands.
>
> A driver can list some files to compile with testpmd, by setting them
> in the testpmd_sources (driver local) meson variable.
> drivers/meson.build then takes care of appending this to a
On Mon, May 23, 2022 at 8:10 PM Ferruh Yigit wrote:
>
> On 5/23/2022 8:10 AM, David Marchand wrote:
> > +int
> > +init_cmdline(void)
> > +{
> > + struct testpmd_commands *c;
> > + cmdline_parse_ctx_t *ctx;
> > + unsigned int count = 0;
> > + unsigned int i;
> > +
> > +
Introduce a testpmd API so that drivers can register specific commands.
A driver can list some files to compile with testpmd, by setting them
in the testpmd_sources (driver local) meson variable.
drivers/meson.build then takes care of appending this to a global meson
variable, and adding the drive
5 matches
Mail list logo
