mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maxime Ripard <mripard@kernel.org>
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 17:34:13 +0200	[thread overview]
Message-ID: <174412644317.1850669.11850198768886971879.b4-ty@kernel.org> (raw)
In-Reply-To: <20250408-drm-kunit-drm-display-mode-memleak-v1-0-996305a2e75a@kernel.org>

On Tue, 08 Apr 2025 09:34:06 +0200, Maxime Ripard wrote:
> 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
> 
> 
> [...]

Applied to misc/kernel.git (drm-misc-fixes).

Thanks!
Maxime

      parent reply	other threads:[~2025-04-08 15:34 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 ` [PATCH 0/7] drm/tests: Fix drm_display_mode memory leaks Thomas Zimmermann
2025-04-08 15:34 ` 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=174412644317.1850669.11850198768886971879.b4-ty@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=phasta@mailbox.org \
    --cc=simona@ffwll.ch \
    --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®