From: Julia Filipchuk <julia.filipchuk@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] Revert "drm/xe/guc: Pre-release GuC firmware v70.24.0 for LNL/BMG/PVC"
Date: Thu, 1 Aug 2024 15:18:08 -0700 [thread overview]
Message-ID: <1685c722-5da2-4195-a0ae-5d50fdcf43c1@intel.com> (raw)
In-Reply-To: <CH0PR11MB5444D0F6C383D3FC861FBE22E5B22@CH0PR11MB5444.namprd11.prod.outlook.com>
On 8/1/2024 1:43 PM, Cavitt, Jonathan wrote:
> Also, may I ask why this revert is needed?
This should create a cleaner merge lower into the drm-tip tree since the
drm-tip branch has changes merged for from the 'topic/xe-for-ci' and
this patch will by applied lower in the tree for upstream.
> ~/proj/drm-tip/drivers/gpu/drm/xe$ git log --oneline -10 origin/drm-tip
> acd846e309e2 (origin/drm-tip, drm-tip) drm-tip: 2024y-07m-30d-14h-17m-47s UTC integration manifest
> 9dda5c1164af Merge remote-tracking branch 'drm-xe/topic/xe-for-CI' into drm-tip
> 517168f6009b Merge remote-tracking branch 'drm-intel/topic/core-for-CI' into drm-tip
> 04dc9413c84e Merge remote-tracking branch 'drm-xe/drm-xe-next' into drm-tip
next prev parent reply other threads:[~2024-08-01 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 20:33 [PATCH 1/3] Revert "drm/xe/guc: Pre-release GuC firmware v70.24.0 for LNL/BMG/PVC" Julia Filipchuk
2024-08-01 20:33 ` [PATCH 2/3] drm/xe/guc: Release GuC v70.29.2 for LNL, BMG Julia Filipchuk
2024-08-01 20:48 ` Cavitt, Jonathan
2024-08-01 20:33 ` [PATCH xe-for-ci 3/3] drm/xe/guc: Pick for-ci GuC firmware for PVC Julia Filipchuk
2024-08-01 20:37 ` Cavitt, Jonathan
2024-08-01 20:40 ` ✓ CI.Patch_applied: success for series starting with [1/3] Revert "drm/xe/guc: Pre-release GuC firmware v70.24.0 for LNL/BMG/PVC" Patchwork
2024-08-01 20:40 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-01 20:41 ` ✓ CI.KUnit: success " Patchwork
2024-08-01 20:43 ` [PATCH 1/3] " Julia Filipchuk
2024-08-01 20:43 ` Cavitt, Jonathan
2024-08-01 22:18 ` Julia Filipchuk [this message]
2024-08-01 20:53 ` ✓ CI.Build: success for series starting with [1/3] " Patchwork
2024-08-01 20:55 ` ✓ CI.Hooks: " Patchwork
2024-08-01 20:56 ` ✓ CI.checksparse: " Patchwork
2024-08-01 21:15 ` ✓ CI.BAT: " Patchwork
2024-08-01 23:24 ` ✗ CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 20:40 [PATCH 0/3] Release GuC v70.29.2 for LNL, BMG Julia Filipchuk
2024-08-01 20:40 ` [PATCH 1/3] Revert "drm/xe/guc: Pre-release GuC firmware v70.24.0 for LNL/BMG/PVC" Julia Filipchuk
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=1685c722-5da2-4195-a0ae-5d50fdcf43c1@intel.com \
--to=julia.filipchuk@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@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