From: "Maxime Ripard" <mripard@kernel.org>
To: "Carlos Eduardo Gallo Filho" <gcarlos@disroot.org>
Cc: dri-devel@lists.freedesktop.org,
"André Almeida" <andrealmeid@igalia.com>,
"Arthur Grillo" <arthurgrillo@riseup.net>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Maíra Canal" <mairacanal@riseup.net>,
"Tales Lelo da Aparecida" <tales.aparecida@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH v3 1/9] drm/tests: Stop using deprecated dev_private member on drm_framebuffer tests
Date: Mon, 08 Jul 2024 11:24:45 +0000 [thread overview]
Message-ID: <95c770cf69b4219c10d4ebd04b2a707e@kernel.org> (raw)
In-Reply-To: <20240703172228.11166-2-gcarlos@disroot.org>
On Wed, 3 Jul 2024 14:22:20 -0300, Carlos Eduardo Gallo Filho wrote:
> The dev_private member of drm_device is deprecated and its use should
> be avoided. Stop using it by embedding the drm_device onto a mock struct.
>
> The new mock struct allows to share variables and even further mocks
> over the tests in a cleaner way than using dev_private void pointer.
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2024-07-08 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 17:22 [PATCH v3 0/9] Increase coverage on drm_framebuffer.c Carlos Eduardo Gallo Filho
2024-07-03 17:22 ` [PATCH v3 1/9] drm/tests: Stop using deprecated dev_private member on drm_framebuffer tests Carlos Eduardo Gallo Filho
2024-07-08 11:24 ` Maxime Ripard [this message]
2024-07-03 17:22 ` [PATCH v3 2/9] drm/tests: Add parameters to the drm_test_framebuffer_create test Carlos Eduardo Gallo Filho
2024-07-08 11:25 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 3/9] drm/tests: Replace strcpy to strscpy on " Carlos Eduardo Gallo Filho
2024-07-08 11:25 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 4/9] drm/tests: Add test case for drm_internal_framebuffer_create() Carlos Eduardo Gallo Filho
2024-07-08 11:28 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 5/9] drm/tests: Add test for drm_framebuffer_check_src_coords() Carlos Eduardo Gallo Filho
2024-07-08 11:28 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 6/9] drm/tests: Add test for drm_framebuffer_cleanup() Carlos Eduardo Gallo Filho
2024-07-08 11:29 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 7/9] drm/tests: Add test for drm_framebuffer_lookup() Carlos Eduardo Gallo Filho
2024-07-08 11:29 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 8/9] drm/tests: Add test for drm_framebuffer_init() Carlos Eduardo Gallo Filho
2024-07-05 5:37 ` kernel test robot
2024-07-08 11:35 ` Maxime Ripard
2024-07-03 17:22 ` [PATCH v3 9/9] drm/tests: Add test for drm_framebuffer_free() Carlos Eduardo Gallo Filho
2024-07-05 11:06 ` kernel test robot
2024-07-08 11:36 ` Maxime Ripard
2024-07-08 16:41 ` Carlos
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=95c770cf69b4219c10d4ebd04b2a707e@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=arthurgrillo@riseup.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gcarlos@disroot.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=tales.aparecida@gmail.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