[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1465398640.25087.50.camel@perches.com>
Date: Wed, 08 Jun 2016 08:10:40 -0700
From: Joe Perches <joe@...ches.com>
To: Roger Quadros <rogerq@...com>, peter.chen@...escale.com
Cc: balbi@...nel.org, tony@...mide.com, gregkh@...uxfoundation.org,
dan.j.williams@...el.com, mathias.nyman@...ux.intel.com,
Joao.Pinto@...opsys.com, sergei.shtylyov@...entembedded.com,
jun.li@...escale.com, grygorii.strashko@...com,
yoshihiro.shimoda.uh@...esas.com, robh@...nel.org, nsekhar@...com,
b-liu@...com, linux-usb@...r.kernel.org,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v9 11/14] usb: otg: use dev_dbg() instead of VDBG()
On Wed, 2016-06-08 at 12:03 +0300, Roger Quadros wrote:
> Now that we have a device reference in struct usb_otg
> let's use dev_dbg() for debug messages.
dev_vdbg vs dev_dbg
The patch subject and commit message don't match the code changes.
> diff --git a/drivers/usb/common/usb-otg-fsm.c b/drivers/usb/common/usb-otg-fsm.c
[]
> @@ -44,8 +37,9 @@ static int otg_set_protocol(struct otg_fsm *fsm, int protocol)
> int ret = 0;
>
> if (fsm->protocol != protocol) {
> - VDBG("Changing role fsm->protocol= %d; new protocol= %d\n",
> - fsm->protocol, protocol);
> + dev_vdbg(otg->dev,
> + "Changing role fsm->protocol= %d; new protocol= %d\n",
> + fsm->protocol, protocol);
etc...
Powered by blists - more mailing lists