From: Joe Perches <joe@perches.com>
To: Chase Metzger <chasemetzger15@gmail.com>
Cc: gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
hdegoede@redhat.com, oneukum@suse.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/usb/core: devio.c: Removed various errors and warnings generated by checkpatch.pl
Date: Sat, 11 Apr 2015 10:20:38 -0700 [thread overview]
Message-ID: <1428772838.5413.58.camel@perches.com> (raw)
In-Reply-To: <1428738815-15373-1-git-send-email-chasemetzger15@gmail.com>
On Sat, 2015-04-11 at 00:53 -0700, Chase Metzger wrote:
> Fixed several errors and warnings.
[]
> Lines 1040 and 1591: changed dev_printk(KERN_DEBUG, ...) to dev_dbg(...).
These changes hav the possibly undesired effect of
removing these messages completely when DEBUG is not
#defined or when CONFIG_DYNAMIC_DEBUG is not enabled
and these messages are not specifically enabled.
> diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
[]
> @@ -1040,7 +1040,7 @@ static int proc_control(struct usb_dev_state *ps, void __user *arg)
> snoop_urb(dev, NULL, pipe, max(i, 0), min(i, 0), COMPLETE, NULL, 0);
> }
> if (i < 0 && i != -EPIPE) {
> - dev_printk(KERN_DEBUG, &dev->dev, "usbfs: USBDEVFS_CONTROL "
> + dev_dbg(&dev->dev, "usbfs: USBDEVFS_CONTROL "
> "failed cmd %s rqt %u rq %u len %u ret %d\n",
> current->comm, ctrl.bRequestType, ctrl.bRequest,
> ctrl.wLength, i);
[]
> @@ -1591,8 +1591,7 @@ static int proc_do_submiturb(struct usb_dev_state *ps, struct usbdevfs_urb *uurb
> }
>
> if (ret) {
> - dev_printk(KERN_DEBUG, &ps->dev->dev,
> - "usbfs: usb_submit_urb returned %d\n", ret);
> + dev_dbg(&ps->dev->dev, "usbfs: usb_submit_urb returned %d\n", ret);
> snoop_urb(ps->dev, as->userurb, as->urb->pipe,
> 0, ret, COMPLETE, NULL, 0);
> async_removepending(as);
next prev parent reply other threads:[~2015-04-11 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 7:53 Chase Metzger
2015-04-11 8:52 ` Hans de Goede
2015-04-11 17:20 ` Joe Perches [this message]
2015-04-28 10:56 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428772838.5413.58.camel@perches.com \
--to=joe@perches.com \
--cc=chasemetzger15@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®