mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Maxime Ripard <mripard@kernel.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: Philipp Stanner <phasta@mailbox.org>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] drm/tests: Fix drm_display_mode memory leaks
Date: Tue, 8 Apr 2025 09:56:06 +0200	[thread overview]
Message-ID: <34f3cdf6-ca11-4eea-aecb-6d7bc5e82a1b@suse.de> (raw)
In-Reply-To: <20250408-drm-kunit-drm-display-mode-memleak-v1-0-996305a2e75a@kernel.org>



Am 08.04.25 um 09:34 schrieb Maxime Ripard:
> Hi,
>
> Here's a series that fixes some memory leaks in our kunit tests that
> eventually show up in kmemleak.
>
> Let me know what you think,
> Maxime
>
> Signed-off-by: Maxime Ripard <mripard@kernel.org>

On the series:

Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>

> ---
> Maxime Ripard (7):
>        drm/tests: helpers: Create kunit helper to destroy a drm_display_mode
>        drm/tests: modeset: Fix drm_display_mode memory leak
>        drm/tests: modeset: Fix drm_display_mode memory leak
>        drm/tests: cmdline: Fix drm_display_mode memory leak
>        drm/tests: modes: Fix drm_display_mode memory leak
>        drm/tests: modes: Fix drm_display_mode memory leak
>        drm/tests: probe-helper: Fix drm_display_mode memory leak
>
>   drivers/gpu/drm/tests/drm_client_modeset_test.c |  9 ++++++++-
>   drivers/gpu/drm/tests/drm_cmdline_parser_test.c | 10 +++++++++-
>   drivers/gpu/drm/tests/drm_kunit_helpers.c       | 23 ++++++++++++++++++++++
>   drivers/gpu/drm/tests/drm_modes_test.c          | 26 +++++++++++++++++++++++++
>   drivers/gpu/drm/tests/drm_probe_helper_test.c   |  8 +++++++-
>   include/drm/drm_kunit_helpers.h                 |  3 +++
>   6 files changed, 76 insertions(+), 3 deletions(-)
> ---
> base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8
> change-id: 20250408-drm-kunit-drm-display-mode-memleak-49d05334c16e
>
> Best regards,

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  parent reply	other threads:[~2025-04-08  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  7:34 Maxime Ripard
2025-04-08  7:34 ` [PATCH 1/7] drm/tests: helpers: Create kunit helper to destroy a drm_display_mode Maxime Ripard
2025-04-08  7:34 ` [PATCH 2/7] drm/tests: modeset: Fix drm_display_mode memory leak Maxime Ripard
2025-04-08  7:34 ` [PATCH 3/7] " Maxime Ripard
2025-04-08  7:34 ` [PATCH 4/7] drm/tests: cmdline: " Maxime Ripard
2025-04-08  7:34 ` [PATCH 5/7] drm/tests: modes: " Maxime Ripard
2025-04-08  7:34 ` [PATCH 6/7] " Maxime Ripard
2025-04-08  7:34 ` [PATCH 7/7] drm/tests: probe-helper: " Maxime Ripard
2025-04-08  7:56 ` Thomas Zimmermann [this message]
2025-04-08 15:34 ` [PATCH 0/7] drm/tests: Fix drm_display_mode memory leaks Maxime Ripard

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=34f3cdf6-ca11-4eea-aecb-6d7bc5e82a1b@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=phasta@mailbox.org \
    --cc=simona@ffwll.ch \
    /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®