From: Simona Vetter <simona.vetter@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Dave Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: Re: [PULL] drm-intel-fixes
Date: Fri, 24 Oct 2025 13:39:12 +0200 [thread overview]
Message-ID: <aPtlYNb5S0ooNqY1@phenom.ffwll.local> (raw)
In-Reply-To: <aPojgsvNYOU0tN4U@intel.com>
On Thu, Oct 23, 2025 at 08:45:54AM -0400, Rodrigo Vivi wrote:
> Hi Dave and Sima,
>
> Here goes our drm-intel-fixes PR with a single fix this round.
>
> Thanks,
> Rodrigo.
>
> drm-intel-fixes-2025-10-23:
> - Fix panic structure allocation memory leak (Jani)
> The following changes since commit 211ddde0823f1442e4ad052a2f30f050145ccada:
>
> Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)
>
> are available in the Git repository at:
>
> https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-fixes-2025-10-23
>
> for you to fetch changes up to 789e46fbfca1875671717a20a916ca1a920268e4:
>
> drm/i915/panic: fix panic structure allocation memory leak (2025-10-20 12:53:57 -0400)
Pulled into drm-fixes, thanks!
-Sima
>
> ----------------------------------------------------------------
> - Fix panic structure allocation memory leak (Jani)
>
> ----------------------------------------------------------------
> Jani Nikula (1):
> drm/i915/panic: fix panic structure allocation memory leak
>
> drivers/gpu/drm/i915/display/intel_fb.c | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
--
Simona Vetter
Software Engineer
http://blog.ffwll.ch
next prev parent reply other threads:[~2025-10-24 11:39 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 12:45 [PULL] drm-intel-fixes Rodrigo Vivi
2025-10-24 11:39 ` Simona Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-09 14:34 Rodrigo Vivi
2026-07-02 6:57 Joonas Lahtinen
2026-06-11 7:32 Tvrtko Ursulin
2026-06-05 10:10 Tvrtko Ursulin
2026-06-04 6:32 Tvrtko Ursulin
2026-05-27 7:55 Tvrtko Ursulin
2026-05-20 7:22 Tvrtko Ursulin
2026-05-13 15:14 Tvrtko Ursulin
2026-05-06 14:39 Tvrtko Ursulin
2026-04-09 10:07 Joonas Lahtinen
2026-04-09 10:24 ` Joonas Lahtinen
2026-04-02 10:21 Joonas Lahtinen
2026-03-26 7:17 Joonas Lahtinen
2026-03-19 7:17 Joonas Lahtinen
2026-03-12 8:54 Tvrtko Ursulin
2026-03-05 7:42 Joonas Lahtinen
2026-02-25 14:40 Joonas Lahtinen
2026-01-15 10:01 Jani Nikula
2025-12-31 17:51 Jani Nikula
2025-11-26 15:44 Rodrigo Vivi
2025-11-20 14:17 Rodrigo Vivi
2025-11-13 13:29 Rodrigo Vivi
2025-11-06 14:31 Rodrigo Vivi
2025-10-30 13:51 Rodrigo Vivi
2025-10-31 18:09 ` Simona Vetter
2025-10-16 12:43 Rodrigo Vivi
2025-09-25 7:38 Tvrtko Ursulin
2025-09-17 15:12 Tvrtko Ursulin
2025-09-10 10:36 Tvrtko Ursulin
2025-08-20 11:48 Tvrtko Ursulin
2025-08-13 21:43 Tvrtko Ursulin
2025-08-14 16:47 ` Imre Deak
2025-07-24 14:36 Rodrigo Vivi
2025-07-17 15:02 Rodrigo Vivi
2025-07-17 18:25 ` Rodrigo Vivi
2025-07-10 22:32 Rodrigo Vivi
2025-07-11 9:35 ` Simona Vetter
2025-07-03 5:29 Joonas Lahtinen
2025-06-26 6:43 Joonas Lahtinen
2025-06-18 6:42 Joonas Lahtinen
2025-05-09 7:30 Jani Nikula
2025-04-30 9:22 Jani Nikula
2025-04-17 7:04 Jani Nikula
2025-04-09 12:41 Jani Nikula
2025-03-13 16:25 Rodrigo Vivi
2025-03-06 17:52 Rodrigo Vivi
2025-02-27 16:22 Rodrigo Vivi
2025-02-20 17:03 Rodrigo Vivi
2025-02-13 17:23 Rodrigo Vivi
2025-02-06 14:11 Rodrigo Vivi
2025-02-06 14:13 ` Rodrigo Vivi
2025-01-15 16:06 Tvrtko Ursulin
2025-01-08 18:18 Tvrtko Ursulin
2024-12-25 13:37 Tvrtko Ursulin
2024-12-18 15:26 Tvrtko Ursulin
2024-12-11 18:04 Tvrtko Ursulin
2024-11-14 7:20 Joonas Lahtinen
2024-10-24 5:59 Joonas Lahtinen
2024-10-17 8:31 Joonas Lahtinen
2024-10-10 7:02 Joonas Lahtinen
2024-10-02 15:25 Joonas Lahtinen
2024-09-12 7:07 Tvrtko Ursulin
2024-09-05 8:16 Tvrtko Ursulin
2024-08-29 7:06 Joonas Lahtinen
2024-08-22 5:40 Joonas Lahtinen
2024-08-08 8:45 Tvrtko Ursulin
[not found] ` <8f7c531a-ecb9-4c30-b4bb-2bdf3056ff34@kernel.org>
[not found] ` <3b87c155-f35d-4812-a4b3-ac5e0bfe0c18@kernel.org>
2024-08-09 7:13 ` Dave Airlie
2024-08-09 8:35 ` Joonas Lahtinen
2024-08-01 6:02 Joonas Lahtinen
2024-07-02 8:28 Jani Nikula
2024-07-04 14:14 ` Daniel Vetter
2024-06-27 8:14 Jani Nikula
2024-06-19 10:45 Jani Nikula
2024-05-30 7:30 Jani Nikula
2024-05-08 19:32 Rodrigo Vivi
2024-04-10 21:51 Rodrigo Vivi
2024-04-04 17:45 Rodrigo Vivi
2024-03-29 1:32 Rodrigo Vivi
2024-03-29 10:23 ` Musial, Ewelina
2024-03-29 13:25 ` Rodrigo Vivi
2024-03-07 8:19 Joonas Lahtinen
2024-03-01 8:14 Joonas Lahtinen
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=aPtlYNb5S0ooNqY1@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).