From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Daniele Ceraolo Spurio" <daniele.ceraolospurio@intel.com>,
"Sharma, Swati2" <swati2.sharma@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dmc: Use firmware v2.06 for TGL
Date: Thu, 05 Mar 2020 10:44:29 +0200 [thread overview]
Message-ID: <87tv33nqc2.fsf@intel.com> (raw)
In-Reply-To: <463117c6-5b0f-00c9-8c43-abffbafaad1a@intel.com>
On Wed, 04 Mar 2020, Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> wrote:
> On 3/3/20 1:29 AM, Jani Nikula wrote:
>> Please ensure 2.06 is in linux-firmware upstream before v5.7 kernel
>> release.
>
> I've just sent the PR to linux-firmware so it shouldn't be an issue to
> get the binary upstream in time for 5.6, but isn't this patch going to
> hit 5.7?
That's what I wrote above didn't I? Surely I wouldn't be off by one! ;D
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-05 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 23:50 [Intel-gfx] [PATCH] drm/i915/dmc: Use firmware v2.06 for TGL José Roberto de Souza
2020-02-28 4:48 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-02-28 6:17 ` [Intel-gfx] [PATCH] " Sharma, Swati2
2020-02-28 7:19 ` Jani Nikula
2020-02-28 11:49 ` Sharma, Swati2
2020-03-03 9:29 ` Jani Nikula
2020-03-04 21:44 ` Daniele Ceraolo Spurio
2020-03-05 8:44 ` Jani Nikula [this message]
2020-02-28 8:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Use firmware v2.06 for TGL (rev2) Patchwork
2020-02-28 12:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Use firmware v2.06 for TGL (rev3) Patchwork
2020-03-01 2:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=87tv33nqc2.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=swati2.sharma@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