From: Myeonghun Pak <mhun512@gmail.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Sumit Semwal <sumit.semwal@linaro.org>,
Casey Connolly <casey.connolly@linaro.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Myeonghun Pak <mhun512@gmail.com>
Subject: [PATCH v2 0/3] drm/panel: switch panel registration to devm_drm_panel_add()
Date: Thu, 23 Apr 2026 21:59:19 +0900 [thread overview]
Message-ID: <20260423125922.57428-1-mhun512@gmail.com> (raw)
This respins the previous attach-failure fixes as a single series.
drm-misc-next now has devm_drm_panel_add() in commit e43a8e3ad8fa
("drm/panel: add devm_drm_panel_add() helper"), so convert the three
affected panel drivers to the managed helper instead of open-coding
drm_panel_remove() in their failure and remove paths.
Changes in v2:
- group the three related panel fixes into one series
- rebase onto drm-misc-next and use devm_drm_panel_add()
- drop manual drm_panel_remove() handling from probe/remove
Myeonghun Pak (3):
drm/panel: ilitek-ili9881c: use devm_drm_panel_add()
drm/panel: jdi-fhd-r63452: use devm_drm_panel_add()
drm/panel: lg-sw43408: use devm_drm_panel_add()
drivers/gpu/drm/panel/panel-ilitek-ili9881c.c | 7 +++----
drivers/gpu/drm/panel/panel-jdi-fhd-r63452.c | 7 +++----
drivers/gpu/drm/panel/panel-lg-sw43408.c | 10 +++++-----
3 files changed, 11 insertions(+), 13 deletions(-)
--
2.47.1
next reply other threads:[~2026-04-23 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 12:59 Myeonghun Pak [this message]
2026-04-23 12:59 ` [PATCH v2 1/3] drm/panel: ilitek-ili9881c: use devm_drm_panel_add() Myeonghun Pak
2026-04-23 12:59 ` [PATCH v2 2/3] drm/panel: jdi-fhd-r63452: " Myeonghun Pak
2026-04-23 12:59 ` [PATCH v2 3/3] drm/panel: lg-sw43408: " Myeonghun Pak
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=20260423125922.57428-1-mhun512@gmail.com \
--to=mhun512@gmail.com \
--cc=airlied@gmail.com \
--cc=casey.connolly@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.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: 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