From: Jani Nikula <jani.nikula@intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Haoxiang Li <haoxiang_li2024@163.com>, stable@vger.kernel.org
Subject: Re: [PATCH 1/7] drm/i915/display: Add check for alloc_ordered_workqueue() and alloc_workqueue()
Date: Tue, 20 May 2025 21:10:32 +0300 [thread overview]
Message-ID: <87ecwjtap3.fsf@intel.com> (raw)
In-Reply-To: <8c1002cd-e5bf-4d1b-880c-5e7ac7d08f70@intel.com>
On Fri, 16 May 2025, Matthew Auld <matthew.auld@intel.com> wrote:
> On 16/05/2025 13:16, Jani Nikula wrote:
>> From: Haoxiang Li <haoxiang_li2024@163.com>
>>
>> Add check for the return value of alloc_ordered_workqueue()
>> and alloc_workqueue(). Furthermore, if some allocations fail,
>> cleanup works are added to avoid potential memory leak problem.
>>
>> Fixes: 40053823baad ("drm/i915/display: move modeset probe/remove functions to intel_display_driver.c")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Haoxiang Li <haoxiang_li2024@163.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Thanks for the review, pushed the lot to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-20 18:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 12:16 [PATCH 0/7] drm/i915 & drm/xe: prep work towards opaque struct intel_display Jani Nikula
2025-05-16 12:16 ` [PATCH 1/7] drm/i915/display: Add check for alloc_ordered_workqueue() and alloc_workqueue() Jani Nikula
2025-05-16 14:04 ` Matthew Auld
2025-05-20 18:10 ` Jani Nikula [this message]
2025-05-16 12:16 ` [PATCH 2/7] drm/xe/display: Add check for alloc_ordered_workqueue() Jani Nikula
2025-05-16 14:05 ` Matthew Auld
2025-05-16 12:16 ` [PATCH 3/7] drm/xe/display: drop duplicate display->fb_tracking.lock init Jani Nikula
2025-05-16 12:16 ` [PATCH 4/7] drm/i915/display: move hotplug.dp_wq init from xe and i915 to display Jani Nikula
2025-05-16 14:11 ` Matthew Auld
2025-05-16 12:16 ` [PATCH 5/7] drm/xe/display: move xe->display initialization to xe_display_probe() Jani Nikula
2025-05-16 14:24 ` Matthew Auld
2025-05-16 12:16 ` [PATCH 6/7] drm/xe/display: add notes about how early a few functions can be called Jani Nikula
2025-05-16 14:25 ` Matthew Auld
2025-05-16 12:17 ` [PATCH 7/7] drm/xe/display: use xe->display to decide whether to do anything Jani Nikula
2025-05-16 14:27 ` Matthew Auld
2025-05-16 12:53 ` ✗ Fi.CI.SPARSE: warning for drm/i915 & drm/xe: prep work towards opaque struct intel_display Patchwork
2025-05-16 13:16 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-19 11:39 ` Jani Nikula
2025-05-16 13:19 ` ✓ CI.Patch_applied: " Patchwork
2025-05-16 13:19 ` ✓ CI.checkpatch: " Patchwork
2025-05-16 13:20 ` ✓ CI.KUnit: " Patchwork
2025-05-16 13:30 ` ✓ CI.Build: " Patchwork
2025-05-16 13:33 ` ✓ CI.Hooks: " Patchwork
2025-05-16 13:34 ` ✓ CI.checksparse: " Patchwork
2025-05-16 13:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-17 8:26 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-19 18:36 ` ✗ i915.CI.Full: " Patchwork
2025-05-20 12:06 ` ✗ Fi.CI.SPARSE: warning for drm/i915 & drm/xe: prep work towards opaque struct intel_display (rev2) Patchwork
2025-05-20 12:33 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-20 14:14 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-27 3:03 ` ✗ CI.Patch_applied: failure for drm/i915 & drm/xe: prep work towards opaque struct intel_display 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=87ecwjtap3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=haoxiang_li2024@163.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.