From: Julia Lawall <julia.lawall@lip6.fr>
To: kernel-janitors@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: is_err checking
Date: Sat, 23 Jul 2016 14:56:14 +0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1607231653440.3490@hadrien> (raw)
Code like the following looks a bit clunky to me:
if (IS_ERR(data->clk) && PTR_ERR(data->clk) != -EPROBE_DEFER)
Is there any reason not to always use eg
data->clk = ERR_PTR(-EPROBE_DEFER)
Code of the latter form is a bit more popular. Perhaps one could want
something like:
IS_ERR_VALUE(data->clk, -EPROBE_DEFER)
but IS_ERR_VALUE is laready used for something else.
julia
next reply other threads:[~2016-07-23 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 14:56 Julia Lawall [this message]
2016-07-24 13:17 ` is_err checking walter harms
2016-07-24 15:37 ` Julia Lawall
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=alpine.DEB.2.10.1607231653440.3490@hadrien \
--to=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox