From: Javier Martinez Canillas <javierm@redhat.com> To: linux-kernel@vger.kernel.org Cc: linux-fbdev@vger.kernel.org, "Thomas Zimmermann" <tzimmermann@suse.de>, "Helge Deller" <deller@gmx.de>, "Javier Martinez Canillas" <javierm@redhat.com>, "Noralf Trønnes" <noralf@tronnes.org>, dri-devel@lists.freedesktop.org, "Jaya Kumar" <jayalk@intworks.biz> Subject: [PATCH 0/3] Fixes and cleanup for DRM fbdev emulation and deferred I/O Date: Fri, 20 Jan 2023 13:08:19 +0100 [thread overview] Message-ID: <20230120120822.2536032-1-javierm@redhat.com> (raw) Hello, This patch series contains two fixes and a cleanup for things that I noticed while debugging a regression in the fbdev emulation for a DRM driver. The first two patches are trivial and shoulnd't be controversial, the third patch is less trivial, but it has been already reviewed by Thomas and I did test it to make sure that works as expected. With it, I got rid of the WARN that happened due a mutex used after it has been destroyed. Best regards, Javier Javier Martinez Canillas (3): fbdev: Remove unused struct fb_deferred_io .first_io field drm/fb-helper: Check fb_deferred_io_init() return value drm/fb-helper: Use a per-driver FB deferred I/O handler drivers/gpu/drm/drm_fbdev_generic.c | 15 ++++++++------- drivers/video/fbdev/core/fb_defio.c | 4 ---- include/drm/drm_fb_helper.h | 10 ++++++++++ include/linux/fb.h | 1 - 4 files changed, 18 insertions(+), 12 deletions(-) -- 2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javierm@redhat.com> To: linux-kernel@vger.kernel.org Cc: "Noralf Trønnes" <noralf@tronnes.org>, "Thomas Zimmermann" <tzimmermann@suse.de>, "Maxime Ripard" <mripard@kernel.org>, "Javier Martinez Canillas" <javierm@redhat.com>, "Daniel Vetter" <daniel@ffwll.ch>, "David Airlie" <airlied@gmail.com>, "Helge Deller" <deller@gmx.de>, "Jaya Kumar" <jayalk@intworks.biz>, "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org Subject: [PATCH 0/3] Fixes and cleanup for DRM fbdev emulation and deferred I/O Date: Fri, 20 Jan 2023 13:08:19 +0100 [thread overview] Message-ID: <20230120120822.2536032-1-javierm@redhat.com> (raw) Hello, This patch series contains two fixes and a cleanup for things that I noticed while debugging a regression in the fbdev emulation for a DRM driver. The first two patches are trivial and shoulnd't be controversial, the third patch is less trivial, but it has been already reviewed by Thomas and I did test it to make sure that works as expected. With it, I got rid of the WARN that happened due a mutex used after it has been destroyed. Best regards, Javier Javier Martinez Canillas (3): fbdev: Remove unused struct fb_deferred_io .first_io field drm/fb-helper: Check fb_deferred_io_init() return value drm/fb-helper: Use a per-driver FB deferred I/O handler drivers/gpu/drm/drm_fbdev_generic.c | 15 ++++++++------- drivers/video/fbdev/core/fb_defio.c | 4 ---- include/drm/drm_fb_helper.h | 10 ++++++++++ include/linux/fb.h | 1 - 4 files changed, 18 insertions(+), 12 deletions(-) -- 2.39.0
next reply other threads:[~2023-01-20 12:08 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-20 12:08 Javier Martinez Canillas [this message] 2023-01-20 12:08 ` [PATCH 0/3] Fixes and cleanup for DRM fbdev emulation and deferred I/O Javier Martinez Canillas 2023-01-20 12:08 ` [PATCH 1/3] fbdev: Remove unused struct fb_deferred_io .first_io field Javier Martinez Canillas 2023-01-20 12:08 ` Javier Martinez Canillas 2023-01-20 12:17 ` Thomas Zimmermann 2023-01-20 12:17 ` Thomas Zimmermann 2023-01-20 12:08 ` [PATCH 2/3] drm/fb-helper: Check fb_deferred_io_init() return value Javier Martinez Canillas 2023-01-20 12:08 ` Javier Martinez Canillas 2023-01-20 12:20 ` Thomas Zimmermann 2023-01-20 12:20 ` Thomas Zimmermann 2023-01-20 12:08 ` [PATCH 3/3] drm/fb-helper: Use a per-driver FB deferred I/O handler Javier Martinez Canillas 2023-01-20 12:08 ` Javier Martinez Canillas 2023-01-21 4:00 ` kernel test robot 2023-01-21 4:00 ` kernel test robot
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=20230120120822.2536032-1-javierm@redhat.com \ --to=javierm@redhat.com \ --cc=deller@gmx.de \ --cc=dri-devel@lists.freedesktop.org \ --cc=jayalk@intworks.biz \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=noralf@tronnes.org \ --cc=tzimmermann@suse.de \ /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: linkBe 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.