Re: [dpdk-dev] [PATCH v2 00/28] sched: feature enhancements

[Thomas Monjalon <thomas@monjalon.net>]

25/06/2019 17:31, Jasvinder Singh:
> Jasvinder Singh (27):
>   sched: update macros for flexible config
>   sched: update subport and pipe data structures
>   sched: update internal data structures
>   sched: update port config API
>   sched: update port free API
>   sched: update subport config API
>   sched: update pipe profile add API
>   sched: update pipe config API
>   sched: update pkt read and write API
>   sched: update subport and tc queue stats
>   sched: update port memory footprint API
>   sched: update packet enqueue API
>   sched: update grinder pipe and tc cache
>   sched: update grinder next pipe and tc functions
>   sched: update pipe and tc queues prefetch
>   sched: update grinder wrr compute function
>   sched: modify credits update function
>   sched: update mbuf prefetch function
>   sched: update grinder schedule function
>   sched: update grinder handle function
>   sched: update packet dequeue API
>   sched: update sched queue stats API
>   test/sched: update unit test
>   net/softnic: update softnic tm function
>   examples/qos_sched: update qos sched sample app
>   examples/ip_pipeline: update ip pipeline sample app
>   sched: code cleanup

I feel the titles of type "update some API" might be more meaningful
if giving the intent (flexibility) or more context (what is updated).
Not sure because I don't know this library enough.