public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Artur Bujdoso <artur.bujdoso@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon-usb: remove unnecessary parentheses
Date: Fri, 8 Apr 2022 10:13:58 +0200	[thread overview]
Message-ID: <Yk/uxoi4VUaR9OpO@kroah.com> (raw)
In-Reply-To: <Yk/knRtaujd/PzK7@crux>

On Fri, Apr 08, 2022 at 09:30:37AM +0200, Artur Bujdoso wrote:
> Adhere to Linux kernel coding style.
> 
> Reported by checkpatch:
> 
> CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses
> 
> Signed-off-by: Artur Bujdoso <artur.bujdoso@gmail.com>
> ---
>  drivers/staging/octeon-usb/octeon-hcd.c | 62 ++++++++++++-------------
>  1 file changed, 31 insertions(+), 31 deletions(-)
> 
> diff --git a/drivers/staging/octeon-usb/octeon-hcd.c b/drivers/staging/octeon-usb/octeon-hcd.c
> index a1cd81d4a114..32bcd6c582f5 100644
> --- a/drivers/staging/octeon-usb/octeon-hcd.c
> +++ b/drivers/staging/octeon-usb/octeon-hcd.c
> @@ -1101,9 +1101,9 @@ static struct cvmx_usb_pipe *cvmx_usb_open_pipe(struct octeon_hcd *usb,
>  	pipe = kzalloc(sizeof(*pipe), GFP_ATOMIC);
>  	if (!pipe)
>  		return NULL;
> -	if ((device_speed == CVMX_USB_SPEED_HIGH) &&
> -	    (transfer_dir == CVMX_USB_DIRECTION_OUT) &&
> -	    (transfer_type == CVMX_USB_TRANSFER_BULK))
> +	if (device_speed == CVMX_USB_SPEED_HIGH &&
> +	    transfer_dir == CVMX_USB_DIRECTION_OUT &&
> +	    transfer_type == CVMX_USB_TRANSFER_BULK)
>  		pipe->flags |= CVMX_USB_PIPE_FLAGS_NEED_PING;

Nah, the original is fine, no need to change this.

Unless, do you have this hardware?  If so, getting this out of staging
would be nice to have happen one day.

thanks,

greg k-h

  reply	other threads:[~2022-04-08  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  7:30 [PATCH] staging: octeon-usb: remove unnecessary parentheses Artur Bujdoso
2022-04-08  8:13 ` Greg Kroah-Hartman [this message]
2022-04-28 12:14   ` Artur Bujdoso
2022-05-05 21:16     ` Greg Kroah-Hartman

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=Yk/uxoi4VUaR9OpO@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=artur.bujdoso@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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