Merged, patches 2 and 3 to master.
Patch 1/3 to api-next, then to next. Maxim. On 07/13/16 19:59, Bill Fischofer wrote:
From: Barry Spinney <spin...@mellanox.com> This todo just asks a question which is no longer important. Signed-off-by: Barry Spinney <spin...@mellanox.com> Signed-off-by: Bill Fischofer <bill.fischo...@linaro.org> --- include/odp/api/spec/traffic_mngr.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/include/odp/api/spec/traffic_mngr.h b/include/odp/api/spec/traffic_mngr.h index 83b89e7..281a749 100644 --- a/include/odp/api/spec/traffic_mngr.h +++ b/include/odp/api/spec/traffic_mngr.h @@ -93,7 +93,6 @@ extern "C" { * @def ODP_TM_MAX_TM_NODE_FANIN * The largest number of fan-in "inputs" that can be simultaneously connected * to a single tm_node. - * @todo Does this need to be as large as ODP_TM_MAX_TM_QUEUES? *//**@@ -880,7 +879,7 @@ typedef struct { /** In the case that sched_modes for a given strict priority level * indicates the use of weighted scheduling, this field supplies the * weighting factors. The weights - when defined - are used such that - * the (adjusted) frame lengths are divided by these 8-bit weights + * the (adjusted) frame lengths are divided by these 8-bit weights * (i.e. they are divisors and not multipliers). Consequently a * weight of 0 (when sched_mode is ODP_TM_BYTE_BASED_WEIGHTS) is * illegal. */
