From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org,
Carlos Eduardo Gallo Filho <gcarlos@disroot.org>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Maíra Canal" <mairacanal@riseup.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Arthur Grillo" <arthurgrillo@riseup.net>,
"Tales Lelo da Aparecida" <tales.aparecida@gmail.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>
Subject: Re: [PATCH v4 RESEND 0/9] Increase coverage on drm_framebuffer.c
Date: Fri, 13 Sep 2024 10:31:08 +0300 [thread overview]
Message-ID: <87ttekdn7n.fsf@intel.com> (raw)
In-Reply-To: <172605715531.956551.13163712003461695066.b4-ty@kernel.org>
On Wed, 11 Sep 2024, Maxime Ripard <mripard@kernel.org> wrote:
> On Tue, 10 Sep 2024 21:15:25 -0300, Carlos Eduardo Gallo Filho wrote:
>> This patchset includes new KUnit tests for 5 untested functions from
>> drm_framebuffer.c and improvements to the existent one.
>>
>> The first patch replace the use of dev_private member from drm_device
>> mock on the existent test by embedding it into an outer struct containing
>> a generic pointer.
>>
>> [...]
>
> Applied to misc/kernel.git (drm-misc-next).
How was this series itself tested? It would be prudent to Cc: intel-gfx
on stuff like this to run it through our CI. I don't think it ever
passed [1].
BR,
Jani.
[1] https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=drm_framebuffer
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-13 7:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 0:15 [PATCH v4 RESEND 0/9] Increase coverage on drm_framebuffer.c Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 1/9] drm/tests: Stop using deprecated dev_private member on drm_framebuffer tests Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 2/9] drm/tests: Add parameters to the drm_test_framebuffer_create test Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 3/9] drm/tests: Replace strcpy to strscpy on " Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 4/9] drm/tests: Add test case for drm_internal_framebuffer_create() Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 5/9] drm/tests: Add test for drm_framebuffer_check_src_coords() Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 6/9] drm/tests: Add test for drm_framebuffer_cleanup() Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 7/9] drm/tests: Add test for drm_framebuffer_lookup() Carlos Eduardo Gallo Filho
2024-09-11 0:15 ` [PATCH v4 RESEND 8/9] drm/tests: Add test for drm_framebuffer_init() Carlos Eduardo Gallo Filho
2024-09-16 8:48 ` Jani Nikula
2024-09-11 0:15 ` [PATCH v4 RESEND 9/9] drm/tests: Add test for drm_framebuffer_free() Carlos Eduardo Gallo Filho
2024-09-11 12:19 ` [PATCH v4 RESEND 0/9] Increase coverage on drm_framebuffer.c Maxime Ripard
2024-09-13 7:31 ` Jani Nikula [this message]
2024-09-13 7:41 ` Maxime Ripard
2024-09-13 9:13 ` Jani Nikula
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=87ttekdn7n.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=arthurgrillo@riseup.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gcarlos@disroot.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=mripard@kernel.org \
--cc=simona.vetter@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.