Re: [PATCH] caif: Use UTILITY_NAME_LENGTH instead of hard-coding 16

From: Jiri Pirko
Date: Mon Mar 18 2024 - 05:26:56 EST

Next message: Naresh Kamboju: "net/sunrpc/sched.c: error: result of comparison against a string literal is unspecified (use an explicit string comparison function instead)"
Previous message: Swapnil Sapkal: "[PATCH v3 1/1] sched: Report the different kinds of imbalances in /proc/schedstat"
In reply to: Christophe JAILLET: "Re: [PATCH] caif: Use UTILITY_NAME_LENGTH instead of hard-coding 16"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Sat, Mar 16, 2024 at 11:16:10AM CET, christophe.jaillet@xxxxxxxxxx wrote:
>UTILITY_NAME_LENGTH is 16. So better use the former when defining the
>'utility_name' array. This makes the intent clearer when it is used around
>line 260.
>
>Signed-off-by: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>

This is net-next material, yet net-next is closed.

https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle

pw-bot: defer

Next message: Naresh Kamboju: "net/sunrpc/sched.c: error: result of comparison against a string literal is unspecified (use an explicit string comparison function instead)"
Previous message: Swapnil Sapkal: "[PATCH v3 1/1] sched: Report the different kinds of imbalances in /proc/schedstat"
In reply to: Christophe JAILLET: "Re: [PATCH] caif: Use UTILITY_NAME_LENGTH instead of hard-coding 16"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]