From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Subject: Re: [PATCH v7 2/2] drm/i915/selftests: Run vma tests only if current->mm is present
Date: Fri, 24 Apr 2026 11:52:32 +0200 [thread overview]
Message-ID: <DI1AK5I0GGGY.1PKOHQ807N9RK@intel.com> (raw)
In-Reply-To: <20260421061716.3341529-3-krzysztof.karas@intel.com>
Hi Krzysztof,
On Tue Apr 21, 2026 at 8:17 AM CEST, Krzysztof Karas wrote:
> This set of tests require userspace memory to map objects,
> so run them only if that memory is available.
>
> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> ---
Looks good to me.
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
next prev parent reply other threads:[~2026-04-24 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 6:17 [PATCH v7 0/2] drm/i915/selftests: Use safe userspace memory for mappings Krzysztof Karas
2026-04-21 6:17 ` [PATCH v7 1/2] drm/i915/selftests: Prevent userspace mapping invalidation Krzysztof Karas
2026-04-24 10:06 ` Sebastian Brzezinka
2026-04-24 11:21 ` Janusz Krzysztofik
2026-04-29 6:12 ` Krzysztof Karas
2026-04-28 14:57 ` Andi Shyti
2026-04-21 6:17 ` [PATCH v7 2/2] drm/i915/selftests: Run vma tests only if current->mm is present Krzysztof Karas
2026-04-24 9:52 ` Sebastian Brzezinka [this message]
2026-04-28 15:03 ` Andi Shyti
2026-04-22 8:51 ` ✓ i915.CI.BAT: success for drm/i915/selftests: Use safe userspace memory for mappings Patchwork
2026-04-22 14:45 ` ✓ i915.CI.Full: " Patchwork
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=DI1AK5I0GGGY.1PKOHQ807N9RK@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.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