public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kushagra Verma <kushagra765@outlook.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB / image: Fix spacing issues in mdc800_endpoint_equals()
Date: Thu, 19 May 2022 12:34:10 +0200	[thread overview]
Message-ID: <YoYdItGTISO4CxHC@kroah.com> (raw)
In-Reply-To: <HK0PR01MB2801F1EE137B9A5196B225D1F8D09@HK0PR01MB2801.apcprd01.prod.exchangelabs.com>

On Thu, May 19, 2022 at 02:42:31PM +0530, Kushagra Verma wrote:
> This patch fixes the following spacing issues in mdc800_endpoint_equals():
> 	1. (Removed) Space between function name and opening parenthesis.
> 	2. (Removed) Space between variable and opening and closing
>             parenthesis in the return statement.
> 	3. (Added) Space between 2 function arguments.
> 
> This fixes multiple checkpatch warnings for this function.
> 
> Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
> ---
>  drivers/usb/image/mdc800.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/image/mdc800.c b/drivers/usb/image/mdc800.c
> index fc0e22cc6fda..dc03e0e54fe0 100644
> --- a/drivers/usb/image/mdc800.c
> +++ b/drivers/usb/image/mdc800.c
> @@ -220,12 +220,12 @@ static struct mdc800_data* mdc800;
>  	The USB Part of the driver
>  ****************************************************************************/
>  
> -static int mdc800_endpoint_equals (struct usb_endpoint_descriptor *a,struct usb_endpoint_descriptor *b)
> +static int mdc800_endpoint_equals(struct usb_endpoint_descriptor *a, struct usb_endpoint_descriptor *b)
>  {
>  	return (
> -		   ( a->bEndpointAddress == b->bEndpointAddress )
> -		&& ( a->bmAttributes     == b->bmAttributes     )
> -		&& ( a->wMaxPacketSize   == b->wMaxPacketSize   )
> +		   (a->bEndpointAddress == b->bEndpointAddress)
> +		&& (a->bmAttributes     == b->bmAttributes)
> +		&& (a->wMaxPacketSize   == b->wMaxPacketSize)

As you can see, the original alignments was done for the specific reason
of making this "pretty".  Your changes really do not help anything here,
which is the primary reason to make checkpatch cleanup changes.

So I'll leave this alone, sorry.

thanks,

greg k-h

      reply	other threads:[~2022-05-19 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  9:12 [PATCH] USB / image: Fix spacing issues in mdc800_endpoint_equals() Kushagra Verma
2022-05-19 10:34 ` Greg KH [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=YoYdItGTISO4CxHC@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kushagra765@outlook.com \
    --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