From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/xe/lnl: Drop force_probe requirement
Date: Tue, 27 Aug 2024 10:49:13 +0300 [thread overview]
Message-ID: <877cc21k3q.fsf@intel.com> (raw)
In-Reply-To: <172473996201.1677393.11744348549360173487.b4-ty@intel.com>
On Mon, 26 Aug 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Thu, 22 Aug 2024 15:46:15 -0700, Lucas De Marchi wrote:
>> Lunar Lake has been usable for a while in a desktop setup. Bugs are
>> sporadically showing up in CI, but being promptly fixed. Nothing very
>> concerning.
>>
>> All the uapi changes related to fundamental platform usage have been
>> finalized.
>>
>> [...]
>
> Applied, thanks for the reviews.
The patch and commit message are all business, but this does mark the
first platform actually supported by the xe driver! Yay!
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-27 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 22:46 [PATCH] drm/xe/lnl: Drop force_probe requirement Lucas De Marchi
2024-08-22 22:51 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-22 22:52 ` ✓ CI.checkpatch: " Patchwork
2024-08-22 22:53 ` ✓ CI.KUnit: " Patchwork
2024-08-22 23:05 ` ✓ CI.Build: " Patchwork
2024-08-22 23:07 ` ✓ CI.Hooks: " Patchwork
2024-08-22 23:08 ` ✓ CI.checksparse: " Patchwork
2024-08-22 23:28 ` ✓ CI.BAT: " Patchwork
2024-08-23 6:06 ` ✗ CI.FULL: failure " Patchwork
2024-08-23 14:30 ` [PATCH] " Rodrigo Vivi
2024-08-23 15:21 ` Thomas Hellström
2024-08-27 6:26 ` Lucas De Marchi
2024-08-27 7:49 ` Jani Nikula [this message]
2024-08-27 16:24 ` Lucas De Marchi
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=877cc21k3q.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.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