From: Jani Nikula <jani.nikula@intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915: use NULL for zero wakeref_t instead of plain integer 0
Date: Fri, 04 Oct 2024 12:27:42 +0300 [thread overview]
Message-ID: <87jzeorze9.fsf@intel.com> (raw)
In-Reply-To: <SJ1PR11MB61295ADC70452548919B3598B9712@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Thu, 03 Oct 2024, "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Wednesday, October 2, 2024 11:47 PM
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>
>> Subject: [PATCH] drm/i915: use NULL for zero wakeref_t instead of plain
>> integer 0
>>
>> As of commit 2edc6a75f26c ("drm/i915: switch intel_wakeref_t underlying
>> type to struct ref_tracker *") we gained quite a few sparse warnings about
>> "Using plain integer as NULL pointer" for using 0 to initialize wakeref_t. Switch
>> to NULL everywhere.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> LGTM
> Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Thanks, pushed to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-04 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 18:16 [PATCH] drm/i915: use NULL for zero wakeref_t instead of plain integer 0 Jani Nikula
2024-10-02 18:52 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-10-02 19:16 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-03 6:45 ` [PATCH] " Borah, Chaitanya Kumar
2024-10-04 9:27 ` Jani Nikula [this message]
2024-10-04 1:42 ` ✗ Fi.CI.IGT: failure for " Patchwork
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=87jzeorze9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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