From: Chewie Lin <linsh@oregonstate.edu>
To: Greg KH <greg@kroah.com>
Cc: forest@alittletooquiet.net, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers/staging/vt6656/main_usb.c: checkpatch warning
Date: Mon, 17 Apr 2017 21:47:53 -0700 [thread overview]
Message-ID: <20170418044752.GA6339@Cassini.Home> (raw)
In-Reply-To: <20170418041411.GA29075@kroah.com>
On Tue, Apr 18, 2017 at 06:14:11AM +0200, Greg KH wrote:
> On Mon, Apr 17, 2017 at 04:58:48PM -0700, Chewie Lin wrote:
> > Swap string in the dev_warn() call with __func__ argument, instead of
> > explicitly calling the function name in the string:
> >
> > WARNING: Prefer using "%s", __func__ to embedded function names
> > #417: FILE: main_usb.c:417:
> > + "usb_device_reset fail status=%d\n", status);
> >
> > total: 0 errors, 1 warnings, 1058 lines checked
> >
> > And after fix:
> >
> > main_usb.c has no obvious style problems and is ready for submission.
> >
> > Signed-off-by: Chewie Lin <linsh@oregonstate.edu>
> > ---
> > drivers/staging/vt6656/main_usb.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/vt6656/main_usb.c b/drivers/staging/vt6656/main_usb.c
> > index 9e074e9daf4e..71c4511b4cff 100644
> > --- a/drivers/staging/vt6656/main_usb.c
> > +++ b/drivers/staging/vt6656/main_usb.c
> > @@ -414,7 +414,7 @@ static void usb_device_reset(struct vnt_private *priv)
> > status = usb_reset_device(priv->usb);
> > if (status)
> > dev_warn(&priv->usb->dev,
> > - "usb_device_reset fail status=%d\n", status);
> > + "%s fail status=%d\n", __func__, status);
>
> But the call that failed was called usb_device_reset(), right? Why is
> this function even needed at all, have the caller call the correct
> function instead please, and then this whole function can be deleted.
>
thanks greg.
Yes, I think that's a good approach as well. I initially wanted to fix a
coding style problem without touching the function calls, but I can
definitely do that as well.
linsh
next prev parent reply other threads:[~2017-04-18 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 23:58 [PATCH 0/1] drivers/staging/vt6656/main_usb.c: checkpatch warning Chewie Lin
2017-04-17 23:58 ` [PATCH 1/1] " Chewie Lin
2017-04-18 4:14 ` Greg KH
2017-04-18 4:47 ` Chewie Lin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-31 10:01 [PATCH] Eudyptula challenge Chewie Lin
2017-03-31 10:01 ` [PATCH 1/1] drivers/staging/vt6656/main_usb.c: checkpatch warning Chewie Lin
2017-03-31 10:32 ` Kim Phillips
2017-03-31 12:33 ` 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=20170418044752.GA6339@Cassini.Home \
--to=linsh@oregonstate.edu \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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