[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X+Gzvo3vPBFGKAy+@kroah.com>
Date: Tue, 22 Dec 2020 09:52:14 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: trix@...hat.com
Cc: b-liu@...com, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: musb: add printf attribute to log function
On Mon, Dec 21, 2020 at 08:25:47AM -0800, trix@...hat.com wrote:
> From: Tom Rix <trix@...hat.com>
>
> Attributing the function allows the compiler to more thoroughly
> check the use of the function with -Wformat and similar flags.
>
> Signed-off-by: Tom Rix <trix@...hat.com>
> ---
> drivers/usb/musb/musb_debug.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/musb/musb_debug.h b/drivers/usb/musb/musb_debug.h
> index e5b3506c7b3f..dfc0d02695fa 100644
> --- a/drivers/usb/musb/musb_debug.h
> +++ b/drivers/usb/musb/musb_debug.h
> @@ -17,6 +17,7 @@
> #define INFO(fmt, args...) yprintk(KERN_INFO, fmt, ## args)
> #define ERR(fmt, args...) yprintk(KERN_ERR, fmt, ## args)
>
> +__printf(2, 3)
> void musb_dbg(struct musb *musb, const char *fmt, ...);
While I understand the need for this, did this find any problems? If
not, then it's not worth adding, the driver-specific debugging macros
should be removed entirely and just use dev_dbg() and friends instead.
thanks,
greg k-h
Powered by blists - more mailing lists