From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Matthew Brost <matthew.brost@intel.com>,
"Dr. David Alan Gilbert" <dave@treblig.org>
Cc: krzysztof.kozlowski@linaro.org, airlied@gmail.com,
mgreer@animalcreek.com, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] ERR_PTR(0) in a couple of places
Date: Mon, 25 Sep 2023 18:09:07 +0300 [thread overview]
Message-ID: <87cyy6mgrw.fsf@intel.com> (raw)
In-Reply-To: <aa6270c5-46d7-4082-ab5a-9a850616b6fe@infradead.org>
On Sun, 24 Sep 2023, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 9/24/23 21:18, Matthew Brost wrote:
>> On Sun, Sep 24, 2023 at 12:41:07AM +0000, Dr. David Alan Gilbert wrote:
>>> Hi,
>>> I randomly noticed there are a couple of places in the kernel that
>>> do
>>> ERR_PTR(0);
>>>
>>> and thought that was odd - shouldn't those just be NULL's ?
>>>
>>> 1) i915
>>> drivers/gpu/drm/i915/gt/uc/selftest_guc_multi_lrc.c : 47
>>>
>>> if (i <= 1)
>>> return ERR_PTR(0);
>>
>> Yes, s/ERR_PTR(0)/ERR_PTR(NULL)/
>>
>> Matt
>
> I agree with Dave's original suggestion since casting NULL isn't needed.
Yeah, s/ERR_PTR(0)/NULL/ would be my choice as well.
As a side note, I generally think it's better not to mix NULL and error
pointers in error return values for a function, because they're harder
to handle properly.
BR,
Jani.
>
>>
>>>
>>> from f9d72092cb490
>>>
>>> 2) trf7970a
>>> drivers/nfc/trf7970a.c : 896
>>>
>>> trf->ignore_timeout =
>>> !cancel_delayed_work(&trf->timeout_work);
>>> trf->rx_skb = ERR_PTR(0);
>>> trf7970a_send_upstream(trf);
>>>
>>> from 1961843ceeca0
>>>
>>> Dave
>>> --
>>> -----Open up your eyes, open up your mind, open up your code -------
>>> / Dr. David Alan Gilbert | Running GNU/Linux | Happy \
>>> \ dave @ treblig.org | | In Hex /
>>> \ _________________________|_____ http://www.treblig.org |_______/
--
Jani Nikula, Intel
prev parent reply other threads:[~2023-09-25 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 0:41 ERR_PTR(0) in a couple of places Dr. David Alan Gilbert
2023-09-24 11:41 ` Krzysztof Kozlowski
2023-09-24 12:16 ` Dr. David Alan Gilbert
2023-09-25 4:18 ` Matthew Brost
2023-09-25 4:25 ` Randy Dunlap
2023-09-25 15:09 ` Jani Nikula [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=87cyy6mgrw.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dave@treblig.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=mgreer@animalcreek.com \
--cc=rdunlap@infradead.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