12/10/2022 15:08, Van Haaren, Harry:
> From: Thomas Monjalon
> > 12/10/2022 14:34, Harry van Haaren:
> > > The eventdev xstats reset API takes an ID of "uint32_t", while
> > > the rest of the xstats APIs require an "unsigned int". On some
> > > platforms these might not be the same bitwidth, howev
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, October 12, 2022 2:06 PM
> To: Van Haaren, Harry
> Cc: dev@dpdk.org; jer...@marvell.com; Li, WeiyuanX ;
> ferruh.yi...@amd.com; andrew.rybche...@oktetlabs.ru; Morten Brørup
>
> Subject: Re: [PATCH
12/10/2022 14:34, Harry van Haaren:
> The eventdev xstats reset API takes an ID of "uint32_t", while
> the rest of the xstats APIs require an "unsigned int". On some
> platforms these might not be the same bitwidth, however this was
> assumed in the code.
>
> Fix by providing a uint32_t to the xst
The eventdev xstats reset API takes an ID of "uint32_t", while
the rest of the xstats APIs require an "unsigned int". On some
platforms these might not be the same bitwidth, however this was
assumed in the code.
Fix by providing a uint32_t to the xstats_reset() function.
Fixes: e21df4b062b5 ("test
4 matches
Mail list logo