Re: [PATCH 0/9] fix kvargs callback prototype not clearly defined

2023-03-09 Thread David Marchand
On Thu, Mar 2, 2023 at 8:56 AM Chengwen Feng wrote: > > The rte_kvargs_process() was used to parse KV pairs, it also supports > to parse 'only keys' (e.g. socket_id) type. And the callback function > parameter 'value' is NULL when parsed 'only keys'. > > But where there is no detailed definition o

Re: [PATCH 0/9] fix kvargs callback prototype not clearly defined

2023-03-02 Thread fengchengwen
Sorry to resend, because the original v1 --cc-cmd failed. On 2023/3/2 15:50, Chengwen Feng wrote: > The rte_kvargs_process() was used to parse KV pairs, it also supports > to parse 'only keys' (e.g. socket_id) type. And the callback function > parameter 'value' is NULL when parsed 'only keys'. >

[PATCH 0/9] fix kvargs callback prototype not clearly defined

2023-03-01 Thread Chengwen Feng
The rte_kvargs_process() was used to parse KV pairs, it also supports to parse 'only keys' (e.g. socket_id) type. And the callback function parameter 'value' is NULL when parsed 'only keys'. But where there is no detailed definition of 'value' maybe NULL. this leads to a lot of processing errors

[PATCH 0/9] fix kvargs callback prototype not clearly defined

2023-03-01 Thread Chengwen Feng
The rte_kvargs_process() was used to parse KV pairs, it also supports to parse 'only keys' (e.g. socket_id) type. And the callback function parameter 'value' is NULL when parsed 'only keys'. But where there is no detailed definition of 'value' maybe NULL. this leads to a lot of processing errors