From: "Summers, Stuart" <stuart.summers@intel.com>
To: "De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "Randhawa, Jagmeet" <jagmeet.randhawa@intel.com>,
"Harrison, John C" <john.c.harrison@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Don't print error about hwconfig when using execlists
Date: Mon, 31 Mar 2025 14:52:07 +0000 [thread overview]
Message-ID: <7cac5e7d8a77487fcb0287d5d9022f89499a65f7.camel@intel.com> (raw)
In-Reply-To: <174343084156.2072291.17379551811561190764.b4-ty@intel.com>
On Mon, 2025-03-31 at 07:22 -0700, Lucas De Marchi wrote:
>
> On Fri, 28 Mar 2025 15:42:36 +0000, Stuart Summers wrote:
> > This error message is only applicable for platforms using
> > GuC submission - to warn the user if the GuC they are using
> > or the platform they are running doesn't have this information
> > to provide to userspace about the platform. When forcing
> > execlist submission, which is something only used for debug,
> > the user is running at their own risk and should understand
> > the limitations of running without GuC.
> >
> > [...]
>
> Applied to drm-xe-next, thanks!
Thanks Lucas!
>
> [1/1] drm/xe: Don't print error about hwconfig when using execlists
> commit: c4eac403519512aef12250cb93ebfdd0966d76f9
>
> Best regards,
prev parent reply other threads:[~2025-03-31 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 15:42 [PATCH] drm/xe: Don't print error about hwconfig when using execlists Stuart Summers
2025-03-28 15:47 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-28 15:47 ` ✓ CI.checkpatch: " Patchwork
2025-03-28 15:49 ` ✓ CI.KUnit: " Patchwork
2025-03-28 16:05 ` ✓ CI.Build: " Patchwork
2025-03-28 16:08 ` ✓ CI.Hooks: " Patchwork
2025-03-28 16:08 ` [PATCH] " John Harrison
2025-03-28 16:09 ` ✓ CI.checksparse: success for " Patchwork
2025-03-28 16:31 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-28 17:07 ` [PATCH] " Randhawa, Jagmeet
2025-03-29 4:23 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-03-31 14:22 ` [PATCH] " Lucas De Marchi
2025-03-31 14:52 ` Summers, Stuart [this message]
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=7cac5e7d8a77487fcb0287d5d9022f89499a65f7.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jagmeet.randhawa@intel.com \
--cc=john.c.harrison@intel.com \
--cc=lucas.demarchi@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