All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH 0/2] Fix kunit test building and missing memory reference
Date: Thu,  2 Mar 2023 13:42:56 +0100	[thread overview]
Message-ID: <20230302124258.91081-1-thomas.hellstrom@linux.intel.com> (raw)

Two small fixes that should help us run (some of) our Kunit tests again.

Thomas Hellström (2):
  drm/xe/tests: Remove CONFIG_FB dependency
  drm/xe/tests: Grab a memory access reference around the migrate sanity
    test

 drivers/gpu/drm/xe/Kconfig.debug      | 1 -
 drivers/gpu/drm/xe/tests/xe_migrate.c | 2 ++
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.39.2


             reply	other threads:[~2023-03-02 12:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 12:42 Thomas Hellström [this message]
2023-03-02 12:42 ` [Intel-xe] [PATCH 1/2] drm/xe/tests: Remove CONFIG_FB dependency Thomas Hellström
2023-03-02 13:06   ` Matthew Auld
2023-03-07 13:47     ` Thomas Hellström
2023-03-02 12:42 ` [Intel-xe] [PATCH 2/2] drm/xe/tests: Grab a memory access reference around the migrate sanity test Thomas Hellström
2023-03-02 13:06   ` Matthew Auld
2023-03-03  6:20   ` Niranjana Vishwanathapura
2023-03-02 13:38 ` [Intel-xe] ✓ CI.Patch_applied: success for Fix kunit test building and missing memory reference Patchwork
2023-03-02 13:39 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-02 13:43 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-03 13:37 ` [Intel-xe] ✓ CI.Patch_applied: " Patchwork
2023-03-03 13:38 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-03 13:41 ` [Intel-xe] ✗ CI.Build: failure " Patchwork
2023-03-03 13:48 ` [Intel-xe] ✓ CI.Patch_applied: success " Patchwork
2023-03-03 13:49 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-03 13:53 ` [Intel-xe] ✓ CI.Build: " 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=20230302124258.91081-1-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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.