From: Joe Perches <joe@perches.com>
To: Tapan Prakash T <tapanprakasht@gmail.com>, mdharm-usb@one-eyed-alien.net
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: usb: storage: onetouch: fixed parethesis and space style issue
Date: Sun, 17 Jan 2016 03:37:20 -0800 [thread overview]
Message-ID: <1453030640.3699.25.camel@perches.com> (raw)
In-Reply-To: <1453024211-9774-1-git-send-email-tapanprakasht@gmail.com>
On Sun, 2016-01-17 at 15:20 +0530, Tapan Prakash T wrote:
> Fixed two coding style issue.
Your email subject is not correct.
This driver is not in staging and there's
a trivial typo in parenthesis.
> diff --git a/drivers/usb/storage/onetouch.c b/drivers/usb/storage/onetouch.c
[]
> @@ -69,7 +69,7 @@ struct usb_onetouch {
> vendorName, productName, useProtocol, useTransport, \
> initFunction, flags) \
> { USB_DEVICE_VER(id_vendor, id_product, bcdDeviceMin, bcdDeviceMax), \
> - .driver_info = (flags) }
> +.driver_info = (flags) }
A more typical style would have been to change
the space to a tab before .driver_info
> static struct usb_device_id onetouch_usb_ids[] = {
> # include "unusual_onetouch.h"
> @@ -125,7 +125,7 @@ static void usb_onetouch_irq(struct urb *urb)
> input_sync(dev);
>
> resubmit:
> - retval = usb_submit_urb (urb, GFP_ATOMIC);
> + retval = usb_submit_urb(urb, GFP_ATOMIC);
> if (retval)
> dev_err(&dev->dev, "can't resubmit intr, %s-%s/input0, "
> "retval %d\n", onetouch->udev->bus->bus_name,
And to coalesce the format string
dev_err(&dev->dev, "can't resubmit intr, %s-%s/input0, retval %d\n",
onetouch->udev->bus->bus_name,
prev parent reply other threads:[~2016-01-17 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 9:50 [PATCH] Staging: usb: storage: onetouch: fixed parethesis and space style issue Tapan Prakash T
2016-01-17 11:37 ` Joe Perches [this message]
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=1453030640.3699.25.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=tapanprakasht@gmail.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.