From b72c60300a8ff850cd0e01cb0fca04ec6f1fd593 Mon Sep 17 00:00:00 2001
From: Egbert Eich <eich@suse.de>
Date: Tue, 18 Jul 2017 16:43:10 +0200
Message-Id: <20170718144320.8354-5-tiwai@suse.de>
Subject: [PATCH 04/14] drm/mgag200: Free container instead of member in
mga_user_framebuffer_destroy()
Patch-mainline: Submitted, dri-devel ML
References: bnc#806990
Technically freeing mga_fb->base is the same as freeing mga_fb as 'base'
the first member of the data structure.
Still this makes it cleaner.
Signed-off-by: Egbert Eich <eich@suse.de>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
drivers/gpu/drm/mgag200/mgag200_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/mgag200/mgag200_main.c b/drivers/gpu/drm/mgag200/mgag200_main.c
index dce8a3eb5a10..cf3a602f453f 100644
--- a/drivers/gpu/drm/mgag200/mgag200_main.c
+++ b/drivers/gpu/drm/mgag200/mgag200_main.c
@@ -20,7 +20,7 @@ static void mga_user_framebuffer_destroy(struct drm_framebuffer *fb)
drm_gem_object_unreference_unlocked(mga_fb->obj);
drm_framebuffer_cleanup(fb);
- kfree(fb);
+ kfree(mga_fb);
}
static const struct drm_framebuffer_funcs mga_fb_funcs = {
--
2.13.2