From: Maxime Ripard <mripard@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jessica.zhang@oss.qualcomm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Casey Connolly <casey.connolly@linaro.org>,
Jerry Han <hanxu5@huaqin.corp-partner.google.com>,
Anusha Srivatsa <asrivats@redhat.com>
Cc: Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/14] drm/panel: Use refcounted allocation in place of devm_kzalloc() - Part5
Date: Wed, 16 Jul 2025 17:37:42 +0200 [thread overview]
Message-ID: <175268024705.1893267.8357084891720845996.b4-ty@kernel.org> (raw)
In-Reply-To: <20250710-b4-driver-convert-last-part-july-v1-0-de73ba81b2f5@redhat.com>
On Thu, 10 Jul 2025 23:31:11 -0500, Anusha Srivatsa wrote:
> Use the new API devm_drm_panel_alloc() for panel allocations.
> A major chunk of driver conversion was sent in a 3 part series
> which is already merged. The coccinelle patch that was used to
> identify unsafe panel allocations didnt flag about 20 drivers.
>
> Not using any semantic patch for the remaining drivers.
> This series does the conversion by not passing explicit type
> to the helper and maintaining type safety suggested by Geert.
>
> [...]
Applied to misc/kernel.git (drm-misc-next).
Thanks!
Maxime
prev parent reply other threads:[~2025-07-16 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 4:31 Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 01/14] drm/panel/lq101r1sx01: Use refcounted allocation in place of devm_kzalloc() Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 02/14] drm/panel/raspberrypi: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 03/14] drm/panel/vvx10f034n00: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 04/14] drm/panel/osd101t2587-53ts: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 05/14] drm/panel/novatek-nt36672a: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 06/14] drm/panel/lg-sw43408: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 07/14] drm/panel/kd097d04: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 08/14] drm/panel/khadas-ts050: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 09/14] drm/panel/jdi-lt070me05000: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 10/14] drm/panel/lpm102a188a: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 11/14] drm/panel/ilitek-ili9882t: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 12/14] drm/panel/himax-hx83102: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 13/14] drm/panel/boe-tv101wum-nl6: " Anusha Srivatsa
2025-07-11 4:31 ` [PATCH 14/14] drm/panel/boe-himax8279d: " Anusha Srivatsa
2025-07-16 15:37 ` Maxime Ripard [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=175268024705.1893267.8357084891720845996.b4-ty@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=asrivats@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=casey.connolly@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=florian.fainelli@broadcom.com \
--cc=hanxu5@huaqin.corp-partner.google.com \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--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
all inboxes | Powered by JetHome®