From: John.C.Harrison@Intel.com
To: linux-firmware@kernel.org
Cc: jwboyer@kernel.org, kyle@kernel.org, ben@decadent.org.uk,
intel-gfx@lists.freedesktop.org
Subject: PR for new GuC v70.13.1
Date: Wed, 18 Oct 2023 12:07:53 -0700 [thread overview]
Message-ID: <20231018190753.2392821-1-John.C.Harrison@Intel.com> (raw)
The following changes since commit 7727f7e3b3358713c7c91c64a835e80c331a6b8b:
Merge branch 'patch-1696561325' into 'main' (2023-10-06 03:04:57 +0000)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware guc_70.13.1
for you to fetch changes up to 44a9510c94ac0334931b6c89dd240ffe5bf1e5fa:
i915: Add GuC v70.13.1 for DG2, TGL, ADL-P and MTL (2023-10-13 11:34:26 -0700)
----------------------------------------------------------------
John Harrison (1):
i915: Add GuC v70.13.1 for DG2, TGL, ADL-P and MTL
WHENCE | 8 ++++----
i915/adlp_guc_70.bin | Bin 297984 -> 342848 bytes
i915/dg2_guc_70.bin | Bin 385856 -> 443200 bytes
i915/mtl_guc_70.bin | Bin 308032 -> 365376 bytes
i915/tgl_guc_70.bin | Bin 285888 -> 330304 bytes
5 files changed, 4 insertions(+), 4 deletions(-)
reply other threads:[~2023-10-18 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231018190753.2392821-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=ben@decadent.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jwboyer@kernel.org \
--cc=kyle@kernel.org \
--cc=linux-firmware@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).