From: Maxime Ripard <mripard@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch, christian.koenig@amd.com,
ray.huang@amd.com, dmitry.baryshkov@linaro.org,
dave.stevenson@raspberrypi.com, quic_jjohnson@quicinc.com,
mcanal@igalia.com, davidgow@google.com,
skhan@linuxfoundation.org, karolina.stolarek@intel.com,
Arunpravin.PaneerSelvam@amd.com,
thomas.hellstrom@linux.intel.com, asomalap@amd.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] drm/tests: Fix some memory leaks
Date: Fri, 25 Oct 2024 16:33:13 +0200 [thread overview]
Message-ID: <20241025-bold-light-vicugna-c30ecf@houat> (raw)
In-Reply-To: <80114de7-19c0-d860-c888-35e535915f78@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Wed, Oct 23, 2024 at 09:35:59AM +0800, Jinjie Ruan wrote:
>
>
> On 2024/10/18 16:12, Jinjie Ruan wrote:
> >
> >
> > On 2024/10/18 15:55, Maxime Ripard wrote:
> >> Hi,
> >>
> >> On Thu, Oct 17, 2024 at 02:31:21PM GMT, Jinjie Ruan wrote:
> >>> Fix some memory leaks in drm tests.
> >>>
> >>> Changes in v3:
> >>> - Adjust drm/drm_edid.h header to drm_kunit_helpers.c.
> >>> - Drop the "helper" in the helper name.
> >>> - s/fllowing/following/
> >>> - Add Acked-by.
> >>
> >> This creates build failures since drm_display_mode were const before,
> >> and can't anymore.
> >
> > It seems it came from bellowing v1, and this v3 has not reported the
> > issue yet.
> >
> > https://lore.kernel.org/all/202410180830.oitxTsOv-lkp@intel.com/
>
> Hi, Maxime,
>
> Should this series send again? The issue seems not related to this version.
As far as I know, the issues reported still apply there, so yes
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2024-10-25 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 6:31 [PATCH v3 0/4] drm/tests: Fix some memory leaks Jinjie Ruan
2024-10-17 6:31 ` [PATCH v3 1/4] drm/tests: helpers: Add helper for drm_display_mode_from_cea_vic() Jinjie Ruan
2024-10-29 8:16 ` Maxime Ripard
2024-10-30 1:48 ` Jinjie Ruan
2024-10-17 6:31 ` [PATCH v3 2/4] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic() Jinjie Ruan
2024-10-17 6:31 ` [PATCH v3 3/4] drm/ttm/tests: Fix memory leak in ttm_tt_simple_create() Jinjie Ruan
2024-10-17 6:31 ` [PATCH v3 4/4] drm/tests: hdmi: Fix memory leaks in drm_display_mode_from_cea_vic() Jinjie Ruan
2024-10-18 7:55 ` [PATCH v3 0/4] drm/tests: Fix some memory leaks Maxime Ripard
2024-10-18 8:07 ` Jinjie Ruan
2024-10-18 8:12 ` Jinjie Ruan
2024-10-23 1:35 ` Jinjie Ruan
2024-10-25 14:33 ` Maxime Ripard [this message]
2024-10-26 2:02 ` Jinjie Ruan
2024-10-29 8:15 ` 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=20241025-bold-light-vicugna-c30ecf@houat \
--to=mripard@kernel.org \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=airlied@gmail.com \
--cc=asomalap@amd.com \
--cc=christian.koenig@amd.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=davidgow@google.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=karolina.stolarek@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=quic_jjohnson@quicinc.com \
--cc=ray.huang@amd.com \
--cc=ruanjinjie@huawei.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=thomas.hellstrom@linux.intel.com \
--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