From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 02/10] drm/i915/fbdev: make intel_framebuffer_create() error return handling explicit
Date: Thu, 18 Sep 2025 20:38:29 +0300 [thread overview]
Message-ID: <aMxDlYYsBXsibtiS@intel.com> (raw)
In-Reply-To: <17631db227d527d6c67f5d6b67adec1ff8dc6f8d.1758184771.git.jani.nikula@intel.com>
On Thu, Sep 18, 2025 at 11:40:52AM +0300, Jani Nikula wrote:
> It's sketchy to pass error pointers via to_intel_framebuffer(). It
> probably works as long as struct intel_framebuffer embeds struct
> drm_framebuffer at offset 0, but be explicit about it.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fbdev_fb.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev_fb.c b/drivers/gpu/drm/i915/display/intel_fbdev_fb.c
> index 210aee9ae88b..b9dfd00a7d05 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev_fb.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev_fb.c
> @@ -67,9 +67,16 @@ struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_fb_helper *helper,
> mode_cmd.pixel_format,
> mode_cmd.modifier[0]),
> &mode_cmd);
> + if (IS_ERR(fb)) {
> + i915_gem_object_put(obj);
> + goto err;
> + }
> +
> i915_gem_object_put(obj);
>
> return to_intel_framebuffer(fb);
> +err:
> + return ERR_CAST(fb);
> }
>
> int intel_fbdev_fb_fill_info(struct intel_display *display, struct fb_info *info,
> --
> 2.47.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-09-18 17:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 8:40 [PATCH v2 00/10] drm/{i915,xe}/fbdev: refactor Jani Nikula
2025-09-18 8:40 ` [PATCH v2 01/10] drm/xe/fbdev: use the same 64-byte stride alignment as i915 Jani Nikula
2025-09-18 17:38 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 02/10] drm/i915/fbdev: make intel_framebuffer_create() error return handling explicit Jani Nikula
2025-09-18 17:38 ` Ville Syrjälä [this message]
2025-09-18 8:40 ` [PATCH v2 03/10] drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_alloc() Jani Nikula
2025-09-18 17:39 ` [PATCH v2 03/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 04/10] drm/{i915, xe}/fbdev: deduplicate struct drm_mode_fb_cmd2 init Jani Nikula
2025-09-18 17:40 ` [PATCH v2 04/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 05/10] drm/i915/fbdev: abstract bo creation Jani Nikula
2025-09-18 17:42 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 06/10] drm/xe/fbdev: " Jani Nikula
2025-09-18 17:42 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 07/10] drm/{i915, xe}/fbdev: add intel_fbdev_fb_bo_destroy() Jani Nikula
2025-09-18 17:43 ` [PATCH v2 07/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 08/10] drm/{i915,xe}/fbdev: deduplicate fbdev creation Jani Nikula
2025-09-18 17:44 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 09/10] drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_fill_info() Jani Nikula
2025-09-18 17:45 ` [PATCH v2 09/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:41 ` [PATCH v2 10/10] drm/i915/fbdev: drop dependency on display in i915 specific code Jani Nikula
2025-09-18 17:50 ` Ville Syrjälä
2025-09-19 7:00 ` Jani Nikula
2025-09-18 8:59 ` ✓ CI.KUnit: success for drm/{i915,xe}/fbdev: refactor (rev2) Patchwork
2025-09-18 9:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 15:54 ` ✓ Xe.CI.Full: " Patchwork
2025-09-18 17:50 ` ✓ i915.CI.BAT: " Patchwork
2025-09-18 21:54 ` ✗ i915.CI.Full: failure " 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=aMxDlYYsBXsibtiS@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.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 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.