From: Jens Axboe <axboe@fb.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] nvme: precedence bug in nvme_pr_clear()
Date: Wed, 09 Dec 2015 17:56:37 +0000 [thread overview]
Message-ID: <56686B55.7020900@fb.com> (raw)
In-Reply-To: <20151209102406.GD3173@mwanda>
On 12/09/2015 03:24 AM, Dan Carpenter wrote:
> The "|" operator has higher precedence than "?:" so this didn't work as
> intended. I had previously fixed this bug, but it we copied the older
> unfixed version when we moved the function between files.
>
> Fixes: 1673f1f08c88 ('nvme: move block_device_operations and ns/ctrl freeing to common code')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Dejavu, but I guess in a different function. Christoph, you are hereby
banned from ever using ?:!
--
Jens Axboe
next prev parent reply other threads:[~2015-12-09 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 10:24 [patch] nvme: precedence bug in nvme_pr_clear() Dan Carpenter
2015-12-09 17:56 ` Jens Axboe [this message]
2015-12-09 18:00 ` Christoph Hellwig
2015-12-09 18:05 ` Jens Axboe
2015-12-09 18:15 ` Keith Busch
2015-12-09 18:00 ` Keith Busch
2015-12-09 18:14 ` Dan Carpenter
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=56686B55.7020900@fb.com \
--to=axboe@fb.com \
--cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).