mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Lundell <jlundell@pobox.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Linux390@de.ibm.com
Subject: Re: if (a & X || b & ~Y) in dasd.c
Date: Thu, 8 Nov 2001 13:18:06 -0800	[thread overview]
Message-ID: <p05100306b810a66e5eb2@[10.128.7.49]> (raw)
In-Reply-To: <20011108155749.A24023@devserv.devel.redhat.com>
In-Reply-To: <20011108155749.A24023@devserv.devel.redhat.com>

At 3:57 PM -0500 11/8/01, Pete Zaitcev wrote:
>Carsten and others:
>
>this code in 2.2.14 looks suspicious to me:
>
>./drivers/s390/block/dasd.c:
>         /* first of all lets try to find out the appropriate era_action */
>         if (stat->flag & DEVSTAT_FLAG_SENSE_AVAIL ||
>             stat->dstat & ~(DEV_STAT_CHN_END | DEV_STAT_DEV_END)) {
>                 /* anything abnormal ? */
>                 if (device->discipline->examine_error == NULL ||
>                     stat->flag & DEVSTAT_HALT_FUNCTION) {
>                         era = dasd_era_fatal;
>                 } else {
>                         era = device->discipline->examine_error (cqr, stat);
>                 }
>                 DASD_DRIVER_DEBUG_EVENT (1, dasd_int_handler," era_code %d",
>                                          era);
>         }
>
>Are you sure any parenthesises are not needed here?

It's OK. You're probably used to seeing (necessary) parens when || is 
replaced by == in this kind of expression.
-- 
/Jonathan Lundell.

  parent reply	other threads:[~2001-11-08 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 20:57 Pete Zaitcev
2001-11-08 21:10 ` Kevin
2001-11-08 21:18 ` Jonathan Lundell [this message]
2001-11-08 21:28 ` Richard B. Johnson
2001-11-19 18:40 ` bill davidsen
2001-11-19 19:38   ` Peter T. Breuer
2001-11-21  6:57   ` Stevie O
2001-11-09 10:29 Carsten Otte

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='p05100306b810a66e5eb2@[10.128.7.49]' \
    --to=jlundell@pobox.com \
    --cc=Linux390@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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 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®