From: Joe Perches <joe@perches.com>
To: roel <roel.kluin@gmail.com>, Jing Huang <huangj@brocade.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: drivers/scsi/bfa/bfa_fcpim.c: boolean and / or confusion
Date: Mon, 12 Dec 2011 16:02:43 -0800 [thread overview]
Message-ID: <1323734563.3837.6.camel@joe2Laptop> (raw)
In-Reply-To: <4EE688FC.8090606@gmail.com>
On Tue, 2011-12-13 at 00:06 +0100, roel wrote:
> The test not [val1] or not [val2] always evaluates to true
Looking at drivers with:
$ grep -rP --include=*.[ch] "(\b[\w\[\]\>\._\-]+)\s*\!\=\s*[\w\[\]\>\._\-]+\s*\)\s*\|\|\s*\(\s*\1\s*\!\=" drivers
drivers/scsi/bfa/bfa_fcpim.c: ((cdb->scsi_cdb[0] != INQUIRY) ||
(cdb->scsi_cdb[0] != REPORT_LUNS))) {
Likely the || should be &&
next parent reply other threads:[~2011-12-13 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EE688FC.8090606@gmail.com>
2011-12-13 0:02 ` Joe Perches [this message]
2011-12-13 0:45 ` drivers/scsi/bfa/bfa_fcpim.c: boolean and / or confusion Jing Huang
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=1323734563.3837.6.camel@joe2Laptop \
--to=joe@perches.com \
--cc=JBottomley@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=huangj@brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=roel.kluin@gmail.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