On Thu, Jul 16, 2015 at 01:28 PM CEST, Sudip Mukherjee
<[email protected]> wrote:
> Stop using DBG_88E which is a custom macro for printing debugging
> messages. Instead start using pr_debug and in the process define
> pr_fmt.
In the end, don't we want to use netdev_dbg() everywhere where we work
with a struct net_device? And use dev_dbg() everywhere where we work
with a struct device (or a struct usb_interface)?
At least that's how I understand commit 8f26b8376faa ("checkpatch:
update suggested printk conversions") description:
Direct conversion of printk(KERN_<LEVEL>... to pr_<level> isn't the
preferred conversion when a struct net_device or struct device is
available.
Do you think it is worth going straight for netdev_dbg()/dev_dbg() to
avoid redoing it later?
>
> Signed-off-by: Sudip Mukherjee <[email protected]>
> ---
> drivers/staging/rtl8188eu/os_dep/usb_intf.c | 39
> +++++++++++++++--------------
> 1 file changed, 20 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/staging/rtl8188eu/os_dep/usb_intf.c
> b/drivers/staging/rtl8188eu/os_dep/usb_intf.c
> index 2d75c77..b245e9c 100644
> --- a/drivers/staging/rtl8188eu/os_dep/usb_intf.c
> +++ b/drivers/staging/rtl8188eu/os_dep/usb_intf.c
> @@ -19,6 +19,7 @@
>
> ******************************************************************************/
> #define _HCI_INTF_C_
>
> +#define pr_fmt(fmt) "R8188EU: " fmt
> #include <osdep_service.h>
> #include <drv_types.h>
> #include <recv_osdep.h>
If we're going to stay with pr_debug(), using KBUILD_MODNAME seems to be
the convention among drivers when defining pr_fmt():
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
Cheers,
Jakub
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
