From: Johan Hovold <johan@kernel.org>
To: Husni Faiz <ahamedhusni73@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] usb: serial: Fix Space Prohibited Coding Style Errors
Date: Mon, 21 Feb 2022 10:37:26 +0100 [thread overview]
Message-ID: <YhNdVtrXnIehZzfy@hovoldconsulting.com> (raw)
In-Reply-To: <20220220131339.179648-1-ahamedhusni73@gmail.com>
On Sun, Feb 20, 2022 at 06:43:39PM +0530, Husni Faiz wrote:
> This patch fixes "space prohibited before that ','" checkpatch error.
> Removed the space after the function argument value "8".
>
> Signed-off-by: Husni Faiz <ahamedhusni73@gmail.com>
> ---
> V1->V2 : Separated the style changes into multiple patches.
As Greg mentioned, please work in drivers/staging if you want to submit
these kind of patches.
checkpatch.pl is great for checking your own patches before submission,
but it shouldn't be run on code that's already in the tree, and where
fixing a white space issue like this one has essentially no value.
And as your staging/greybus submission showed, using the output of tools
like checkpatch.pl even risks breaking things if you take it too
literally and don't use your own judgement.
> drivers/usb/serial/iuu_phoenix.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/serial/iuu_phoenix.c b/drivers/usb/serial/iuu_phoenix.c
> index 0be3b5e1eaf3..2f7784572c4d 100644
> --- a/drivers/usb/serial/iuu_phoenix.c
> +++ b/drivers/usb/serial/iuu_phoenix.c
> @@ -360,7 +360,7 @@ static void iuu_led_activity_on(struct urb *urb)
> usb_fill_bulk_urb(port->write_urb, port->serial->dev,
> usb_sndbulkpipe(port->serial->dev,
> port->bulk_out_endpointAddress),
> - port->write_urb->transfer_buffer, 8 ,
> + port->write_urb->transfer_buffer, 8,
> iuu_rxcmd, port);
> usb_submit_urb(port->write_urb, GFP_ATOMIC);
> }
> @@ -380,7 +380,7 @@ static void iuu_led_activity_off(struct urb *urb)
> usb_fill_bulk_urb(port->write_urb, port->serial->dev,
> usb_sndbulkpipe(port->serial->dev,
> port->bulk_out_endpointAddress),
> - port->write_urb->transfer_buffer, 8 ,
> + port->write_urb->transfer_buffer, 8,
> iuu_rxcmd, port);
> usb_submit_urb(port->write_urb, GFP_ATOMIC);
> }
Johan
next prev parent reply other threads:[~2022-02-21 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 17:55 [PATCH] usb: serial: Fix " Husni Faiz
2022-02-14 10:13 ` Greg KH
2022-02-20 13:13 ` [PATCH v2 1/2] usb: serial: Fix Space Prohibited " Husni Faiz
2022-02-21 9:37 ` Johan Hovold [this message]
2022-02-20 13:14 ` [PATCH v2 2/2] usb: serial: Fix Coding Style Error Around Ternary Operator Husni Faiz
2022-02-21 9:39 ` Johan Hovold
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=YhNdVtrXnIehZzfy@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ahamedhusni73@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®