From: Anusha <anusha.srivatsa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/2] HuC Update for BXT
Date: Fri, 30 Nov 2018 11:05:04 -0800 [thread overview]
Message-ID: <20181130190506.1360-1-anusha.srivatsa@intel.com> (raw)
The following changes since commit 1baa34868b2c0a004dc595b20678145e3fff83e7:
Merge branch 'nxp_mc' of https://github.com/NXP/linux-firmware (2018-10-26 08:13:19 -0400)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware BXT_HUC
for you to fetch changes up to 69f153bbc2c44eb581c1f8c7cecd4d878e4e727a:
firmware/huc/bxt: Add huC Update for BXT (2018-11-28 10:33:57 -0800)
----------------------------------------------------------------
Anusha Srivatsa (1):
firmware/huc/bxt: Add huC Update for BXT
WHENCE | 3 +++
i915/bxt_huc_ver01_8_2893.bin | Bin 0 -> 146880 bytes
2 files changed, 3 insertions(+)
create mode 100644 i915/bxt_huc_ver01_8_2893.bin
Anusha Srivatsa (2):
firmware/huc/BXT: Update the HuC version
HAX enable HuC for CI
drivers/gpu/drm/i915/i915_params.h | 2 +-
drivers/gpu/drm/i915/intel_huc_fw.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.19.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-11-30 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 19:05 Anusha [this message]
2018-11-30 19:05 ` [PATCH 1/2] firmware/huc/BXT: Update the HuC version Anusha
2018-11-30 19:05 ` [PATCH 2/2] HAX enable HuC for CI Anusha
2018-11-30 19:30 ` ✗ Fi.CI.CHECKPATCH: warning for HuC Update for BXT Patchwork
2018-11-30 19:54 ` ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-12-07 18:28 [PATCH 0/2] " Anusha
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=20181130190506.1360-1-anusha.srivatsa@intel.com \
--to=anusha.srivatsa@intel.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox