All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Fabian Baumanis <baumanisf@gmail.com>
Cc: abbotti@mev.co.uk, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, hsweeten@visionengravers.com,
	larturus@yahoo.com
Subject: Re: [PATCH] Staging: comedi: adl_pci9118.c : fixed code style issue
Date: Fri, 24 Nov 2017 16:53:55 +0100	[thread overview]
Message-ID: <20171124155355.GA30433@kroah.com> (raw)
In-Reply-To: <20dcf3e7-7621-a6d1-d50a-0c52e6dcdae3@gmail.com>

On Sat, Nov 18, 2017 at 06:46:38PM +0100, Fabian Baumanis wrote:
> Removed uneccessary parantheses which were sorrounding two
> if-statements.
> 
> Signed-off-by: Fabian Baumanis <baumanisf@gmail.com>
> ---
>  drivers/staging/comedi/drivers/adl_pci9118.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/comedi/drivers/adl_pci9118.c b/drivers/staging/comedi/drivers/adl_pci9118.c
> index 1cc9b7e..c77b994 100644
> --- a/drivers/staging/comedi/drivers/adl_pci9118.c
> +++ b/drivers/staging/comedi/drivers/adl_pci9118.c
> @@ -946,8 +946,7 @@ static int pci9118_ai_cmd(struct comedi_device *dev, struct comedi_subdevice *s)
>         devpriv->ai_add_back = 0;
>         if (devpriv->master) {
>                 devpriv->usedma = 1;
> -               if ((cmd->flags & CMDF_WAKE_EOS) &&
> -                   (cmd->scan_end_arg == 1)) {
> +               if (cmd->flags & CMDF_WAKE_EOS && cmd->scan_end_arg == 1) {

Ick, no, now I need to remember which has higher precedence, "&" or
"&&".  It's "&" right?  I should not have to go look it up.

The code as-is is just fine.

thanks,

greg k-h

      parent reply	other threads:[~2017-11-24 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18 17:46 [PATCH] Staging: comedi: adl_pci9118.c : fixed code style issue Fabian Baumanis
2017-11-20 11:12 ` Ian Abbott
2017-11-24 15:53 ` 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=20171124155355.GA30433@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=baumanisf@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hsweeten@visionengravers.com \
    --cc=larturus@yahoo.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 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.