From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v8 5/5] Staging: emxx_udc: Clean dev_err() logging
Date: Fri, 27 Feb 2015 14:22:55 +0300 [thread overview]
Message-ID: <20150227112255.GA28904@example.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1502271156510.2668@hadrien>
Ok, I'll try that out.
On Fri, Feb 27, 2015 at 11:57:15AM +0100, Julia Lawall wrote:
> Maybe you can try using Coccinelle to find this problem more generally.
>
> julia
>
> On Fri, 27 Feb 2015, Haneen Mohammed wrote:
>
> > This patch removes __func__ from dev_err.
> > dev_err includes the function name in the log printout, so there is no
> > need to include it manually.
> >
> > Signed-off-by: Haneen Mohammed <hamohammed.sa@gmail.com>
> > ---
> > drivers/staging/emxx_udc/emxx_udc.c | 18 +++++++++---------
> > 1 file changed, 9 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/staging/emxx_udc/emxx_udc.c b/drivers/staging/emxx_udc/emxx_udc.c
> > index 77189cc..0bfd268 100644
> > --- a/drivers/staging/emxx_udc/emxx_udc.c
> > +++ b/drivers/staging/emxx_udc/emxx_udc.c
> > @@ -2626,7 +2626,7 @@ static int nbu2ss_ep_enable(
> > if ((ep_type == USB_ENDPOINT_XFER_CONTROL)
> > || (ep_type == USB_ENDPOINT_XFER_ISOC)) {
> >
> > - dev_err(ep->udc->dev, "udc: *** %s, bat bmAttributes\n", __func__);
> > + dev_err(ep->udc->dev, "bat bmAttributes\n");
> > return -EINVAL;
> > }
> >
> > @@ -2637,7 +2637,7 @@ static int nbu2ss_ep_enable(
> > if ((udc->driver == NULL)
> > || (udc->gadget.speed == USB_SPEED_UNKNOWN)) {
> >
> > - dev_err(udc->dev, " *** %s, udc !!\n", __func__);
> > + dev_err(udc->dev, "udc !!\n");
> > return -ESHUTDOWN;
> > }
> >
> > @@ -2778,7 +2778,7 @@ static int nbu2ss_ep_queue(
> > }
> >
> > if (unlikely(!udc->driver)) {
> > - dev_err(udc->dev, "%s, bogus device state %p\n", __func__, udc->driver);
> > + dev_err(udc->dev, "bogus device state %p\n", udc->driver);
> > return -ESHUTDOWN;
> > }
> >
> > @@ -2817,7 +2817,7 @@ static int nbu2ss_ep_queue(
> >
> > result = _nbu2ss_start_transfer(udc, ep, req, FALSE);
> > if (result < 0) {
> > - dev_err(udc->dev, " *** %s, result = %d\n", __func__, result);
> > + dev_err(udc->dev, "result = %d\n", result);
> > list_del(&req->queue);
> > } else if ((ep->epnum > 0) && (ep->direct == USB_DIR_OUT)) {
> > #ifdef USE_DMA
> > @@ -2907,7 +2907,7 @@ static int nbu2ss_ep_set_halt(struct usb_ep *_ep, int value)
> >
> > udc = ep->udc;
> > if (!udc) {
> > - dev_err(ep->udc->dev, "udc: *** %s, bad udc\n", __func__);
> > + dev_err(ep->udc->dev, "bad udc\n");
> > return -EINVAL;
> > }
> >
> > @@ -2961,7 +2961,7 @@ static int nbu2ss_ep_fifo_status(struct usb_ep *_ep)
> >
> > udc = ep->udc;
> > if (!udc) {
> > - dev_err(ep->udc->dev, "udc: %s, bad udc\n", __func__);
> > + dev_err(ep->udc->dev, "bad udc\n");
> > return -EINVAL;
> > }
> >
> > @@ -3009,7 +3009,7 @@ static void nbu2ss_ep_fifo_flush(struct usb_ep *_ep)
> >
> > udc = ep->udc;
> > if (!udc) {
> > - dev_err(ep->udc->dev, "udc: %s, bad udc\n", __func__);
> > + dev_err(ep->udc->dev, "bad udc\n");
> > return;
> > }
> >
> > @@ -3059,7 +3059,7 @@ static int nbu2ss_gad_get_frame(struct usb_gadget *pgadget)
> >
> > udc = container_of(pgadget, struct nbu2ss_udc, gadget);
> > if (udc == NULL) {
> > - dev_err(&pgadget->dev, "%s, udc == NULL\n", __func__);
> > + dev_err(&pgadget->dev, "udc == NULL\n");
> > return -EINVAL;
> > }
> >
> > @@ -3089,7 +3089,7 @@ static int nbu2ss_gad_wakeup(struct usb_gadget *pgadget)
> >
> > udc = container_of(pgadget, struct nbu2ss_udc, gadget);
> > if (udc == NULL) {
> > - dev_err(&pgadget->dev, "%s, udc == NULL\n", __func__);
> > + dev_err(&pgadget->dev, "udc == NULL\n");
> > return -EINVAL;
> > }
> >
> > --
> > 1.9.1
> >
> > --
> > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1425033356-20933-1-git-send-email-hamohammed.sa%40gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
next prev parent reply other threads:[~2015-02-27 11:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 9:48 [PATCH v6 0/4] Staging: emxx_udc: Fix checkpatch.pl warnings Haneen Mohammed
2015-02-27 10:01 ` [PATCH v7 0/5] " Haneen Mohammed
2015-02-27 10:26 ` [PATCH v8 " Haneen Mohammed
2015-02-27 10:28 ` [PATCH v8 1/5] Staging: emxx_udc: Fix do not add new typedefs remove and volatile Haneen Mohammed
2015-02-27 10:31 ` [PATCH v8 2/5] Staging: emxx_udc: Replace custom printk macro ERR with pr_err Haneen Mohammed
2015-02-27 10:59 ` [Outreachy kernel] " Julia Lawall
2015-02-27 11:42 ` Haneen Mohammed
2015-02-27 10:32 ` [PATCH v8 3/5] Staging: emxx_udc: Replace custom printk macro ERR with dev_err Haneen Mohammed
2015-02-27 10:34 ` [PATCH v8 4/5] Staging: emxx_udc: Remove custom printk macro ERR Haneen Mohammed
2015-02-27 10:35 ` [PATCH v8 5/5] Staging: emxx_udc: Clean dev_err() logging Haneen Mohammed
2015-02-27 10:57 ` [Outreachy kernel] " Julia Lawall
2015-02-27 11:22 ` Haneen Mohammed [this message]
2015-03-01 20:53 ` [PATCH v9 0/4] emxx_udc: Fix checkpatch.pl warnings Haneen Mohammed
2015-03-01 20:55 ` [PATCH v9 1/4] Staging: emxx_udc: Fix do not add new typedefs and remove volatile Haneen Mohammed
2015-03-02 1:12 ` [Outreachy kernel] " Greg KH
2015-03-01 21:00 ` [PATCH v9 2/4] Staging: emxx_udc: Replace custom printk macro ERR with dev_err or pr_err Haneen Mohammed
2015-03-01 21:03 ` [PATCH v9 3/4] Staging: emxx_udc: Remove custom printk macro ERR Haneen Mohammed
2015-03-01 21:04 ` [PATCH v9 4/4] Staging: emxx_udc: Clean dev_err() logging Haneen Mohammed
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=20150227112255.GA28904@example.com \
--to=hamohammed.sa@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.