From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Yue Haibing <yuehaibing@huawei.com>,
rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch,
dev@lankhorst.se
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] drm/i915/display: Fix build error without DRM_FBDEV_EMULATION
Date: Fri, 21 Mar 2025 14:41:02 +0200 [thread overview]
Message-ID: <87y0wyblpd.fsf@intel.com> (raw)
In-Reply-To: <12145722-609e-41d0-b02b-059df5b6d17f@suse.de>
On Mon, 17 Mar 2025, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Am 15.03.25 um 13:01 schrieb Yue Haibing:
>> In file included from <command-line>:
>> ./drivers/gpu/drm/i915/display/intel_fbdev.h: In function ‘intel_fbdev_framebuffer’:
>> ./drivers/gpu/drm/i915/display/intel_fbdev.h:32:16: error: ‘NULL’ undeclared (first use in this function)
>> 32 | return NULL;
>> | ^~~~
>> ./drivers/gpu/drm/i915/display/intel_fbdev.h:1:1: note: ‘NULL’ is defined in header ‘<stddef.h>’; did you forget to ‘#include <stddef.h>’?
>> +++ |+#include <stddef.h>
>> 1 | /* SPDX-License-Identifier: MIT */
>> ./drivers/gpu/drm/i915/display/intel_fbdev.h:32:16: note: each undeclared identifier is reported only once for each function it appears in
>> 32 | return NULL;
>> | ^~~~
>>
>> Build fails if CONFIG_DRM_FBDEV_EMULATION is n, add missing header file.
>>
>> Fixes: 9fa154f40eb6 ("drm/{i915,xe}: Run DRM default client setup")
>> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
>
> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
Merged to drm-intel-next, thanks for the patch and ack.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/display/intel_fbdev.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.h b/drivers/gpu/drm/i915/display/intel_fbdev.h
>> index ca2c8c438f02..89bad3a2b01a 100644
>> --- a/drivers/gpu/drm/i915/display/intel_fbdev.h
>> +++ b/drivers/gpu/drm/i915/display/intel_fbdev.h
>> @@ -6,6 +6,8 @@
>> #ifndef __INTEL_FBDEV_H__
>> #define __INTEL_FBDEV_H__
>>
>> +#include <linux/types.h>
>> +
>> struct drm_fb_helper;
>> struct drm_fb_helper_surface_size;
>> struct drm_i915_private;
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-03-21 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 12:01 [PATCH -next] drm/i915/display: Fix build error without DRM_FBDEV_EMULATION Yue Haibing
2025-03-15 12:13 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-15 12:14 ` ✓ CI.checkpatch: " Patchwork
2025-03-15 12:15 ` ✓ CI.KUnit: " Patchwork
2025-03-15 12:31 ` ✓ CI.Build: " Patchwork
2025-03-15 12:34 ` ✓ CI.Hooks: " Patchwork
2025-03-15 12:35 ` ✓ CI.checksparse: " Patchwork
2025-03-15 12:56 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-15 15:25 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-17 8:09 ` [PATCH -next] " Thomas Zimmermann
2025-03-21 12:41 ` 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=87y0wyblpd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
--cc=yuehaibing@huawei.com \
/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