From: "Tolakanahalli Pradeep, Madhumitha" <madhumitha.tolakanahalli.pradeep@intel.com>
To: "jwboyer@kernel.org" <jwboyer@kernel.org>
Cc: "kyle@mcmartin.ca" <kyle@mcmartin.ca>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Hutchings, Ben" <ben@decadent.org.uk>,
"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Subject: Re: [Intel-gfx] i915 Updates: DG2 DMC v2.06
Date: Tue, 3 May 2022 16:51:06 +0000 [thread overview]
Message-ID: <ef5502d7cbdf15e52010609712b7eb4cb233cfe9.camel@intel.com> (raw)
In-Reply-To: <CA+5PVA5vFH6vZQpYsTjsGkuc8_d53YPcuXGxM2EyThmudr8itQ@mail.gmail.com>
On Tue, 2022-05-03 at 08:20 -0400, Josh Boyer wrote:
> On Mon, May 2, 2022 at 3:56 PM Tolakanahalli Pradeep, Madhumitha
> <madhumitha.tolakanahalli.pradeep@intel.com> wrote:
> >
> > The following changes since commit c3624ebd67c68722e0fabc9cae01397b15310239:
> >
> > Merge branch 'ath10k-20220423' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware into main
> > (2022-05-02 08:31:40 -0400)
> >
> > are available in the Git repository at:
> >
> > git://anongit.freedesktop.org/drm/drm-firmware dg2_dmc_v2.06_rebase
> >
> > for you to fetch changes up to b8bd6ccd9c409508a0b424492981721b45c55127:
> >
> > i915: Add DMC v2.06 for DG2 (2022-05-02 22:53:23 +0530)
> >
> > ----------------------------------------------------------------
> > Madhumitha Tolakanahalli Pradeep (1):
> > i915: Add DMC v2.06 for DG2
>
> Pulled and pushed out.
>
> josh
>
Thanks for the super quick merge :)
> >
> > WHENCE | 3 +++
> > i915/dg2_dmc_ver2_06.bin | Bin 0 -> 22416 bytes
> > 2 files changed, 3 insertions(+)
> > create mode 100644 i915/dg2_dmc_ver2_06.bin
> >
prev parent reply other threads:[~2022-05-03 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 19:56 [Intel-gfx] i915 Updates: DG2 DMC v2.06 Tolakanahalli Pradeep, Madhumitha
2022-05-03 12:20 ` Josh Boyer
2022-05-03 16:51 ` Tolakanahalli Pradeep, Madhumitha [this message]
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=ef5502d7cbdf15e52010609712b7eb4cb233cfe9.camel@intel.com \
--to=madhumitha.tolakanahalli.pradeep@intel.com \
--cc=ben@decadent.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jwboyer@kernel.org \
--cc=kyle@mcmartin.ca \
--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