From: "Maxime Ripard" <mripard@kernel.org>
To: "Arthur Grillo" <arthurgrillo@riseup.net>
Cc: andrealmeid@riseup.net, dri-devel@lists.freedesktop.org,
kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org,
mairacanal@riseup.net, tales.aparecida@gmail.com,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"David Gow" <davidgow@google.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Maxime Ripard" <mripard@kernel.org>
Subject: Re: [PATCH 1/3] drm/tests: Fix kunit_release_action ctx argument
Date: Wed, 20 Sep 2023 06:29:42 +0000 [thread overview]
Message-ID: <cf7df9564146d47476d50d43f7b0bbff.mripard@kernel.org> (raw)
In-Reply-To: <20230920-kunit-kasan-fixes-v1-1-1a0fc261832d@riseup.net>
On Wed, 20 Sep 2023 03:11:36 -0300, Arthur Grillo wrote:
> The kunit_action_platform_driver_unregister is added with
> &fake_platform_driver as ctx, but the kunit_release_action is called
> pdev as ctx. Fix that by replacing it with &fake_platform_driver.
>
> Fixes: 4f2b0b583baa ("drm/tests: helpers: Switch to kunit actions")
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2023-09-20 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 6:11 [PATCH 0/3] Fix a couble of bugs in drm_kunit_helpers.c Arthur Grillo
2023-09-20 6:11 ` [PATCH 1/3] drm/tests: Fix kunit_release_action ctx argument Arthur Grillo
2023-09-20 6:29 ` Maxime Ripard [this message]
2023-09-27 22:47 ` Maira Canal
2023-09-27 22:52 ` Arthur Grillo
2023-09-30 15:17 ` Maira Canal
2023-09-20 6:11 ` [PATCH 2/3] kunit: Add kunit_move_action_to_top_or_reset() to reorder actions Arthur Grillo
2023-09-22 8:00 ` David Gow
2023-09-25 9:59 ` Maxime Ripard
2023-09-20 6:11 ` [PATCH 3/3] drm/tests: Fix a use-after-free bug in __drm_kunit_helper_alloc_drm_device() Arthur Grillo
2023-09-20 6:40 ` Maxime Ripard
2023-09-20 6:54 ` Arthur Grillo
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=cf7df9564146d47476d50d43f7b0bbff.mripard@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=andrealmeid@riseup.net \
--cc=arthurgrillo@riseup.net \
--cc=brendan.higgins@linux.dev \
--cc=daniel@ffwll.ch \
--cc=davidgow@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=tales.aparecida@gmail.com \
/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