From: Maxime Ripard <mripard@kernel.org>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Michał Winiarski" <michal.winiarski@intel.com>
Cc: "Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Maíra Canal" <mcanal@igalia.com>
Subject: Re: (subset) [PATCH v5 3/5] drm/tests: managed: Add comments about test intent
Date: Wed, 17 Jan 2024 10:47:06 +0100 [thread overview]
Message-ID: <170548482640.96553.2643651506083718393.b4-ty@kernel.org> (raw)
In-Reply-To: <20240115171351.504264-4-michal.winiarski@intel.com>
On Mon, 15 Jan 2024 18:13:49 +0100, Michał Winiarski wrote:
> Add comments explaining the intention behind the test and certain
> implementation details related to device lifetime.
>
>
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
next prev parent reply other threads:[~2024-01-17 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 17:13 [PATCH v5 0/5] drm/managed: Add drmm_release_action Michał Winiarski
2024-01-15 17:13 ` [PATCH v5 1/5] " Michał Winiarski
2024-01-17 9:47 ` (subset) " Maxime Ripard
2024-01-15 17:13 ` [PATCH v5 2/5] drm/tests: managed: Rename the suite name to match other DRM tests Michał Winiarski
2024-01-17 9:47 ` (subset) " Maxime Ripard
2024-01-15 17:13 ` [PATCH v5 3/5] drm/tests: managed: Add comments about test intent Michał Winiarski
2024-01-17 9:47 ` Maxime Ripard [this message]
2024-01-15 17:13 ` [PATCH v5 4/5] drm/tests: managed: Extract device initialization into test init Michał Winiarski
2024-01-17 9:47 ` (subset) " Maxime Ripard
2024-01-15 17:13 ` [PATCH v5 5/5] drm/tests: managed: Add a simple test for drmm_managed_release Michał Winiarski
2024-01-17 9:47 ` (subset) " 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=170548482640.96553.2643651506083718393.b4-ty@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=rodrigo.vivi@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
all inboxes | Powered by JetHome®