From: o1bigtenor <o1bigtenor@gmail.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
dri-devel@lists.freedesktop.org, Jaroslav Kysela <perex@perex.cz>,
Mark Brown <broonie@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [GIT PULL] HDMI codec improvements, v2
Date: Wed, 23 Jun 2021 08:14:46 -0500 [thread overview]
Message-ID: <CAPpdf58AmzQkAQBx8x_kjfREto9qugYS0jLV+0qfp+atDFRimA@mail.gmail.com> (raw)
In-Reply-To: <20210623121311.qlbnije5gn7o7so7@gilmour>
On Wed, Jun 23, 2021 at 7:13 AM Maxime Ripard <maxime@cerno.tech> wrote:
>
> On Thu, Jun 10, 2021 at 02:25:50PM +0200, Maxime Ripard wrote:
> > Hi,
> >
> > Here's a PR for the changes to hdmi-codec that need to be shared between
> > drm-misc-next and ASoC.
> >
> > This is the second iteration, fixing a bisection issue with compilation
> >
> > Thanks!
> > Maxime
>
> Merged into drm-misc-next
>
Not sure if its applicable - - - - - but - - - - I've been waiting
wanting to use a 4k monitor on hdmi for a number of months now. There
is a bug filed where I wasgiven to believe that my issues were likely quite
connected with hdmi.
I would be quite interested in seeing any hdmi fixes also added into 5.10.????
kernels not only the 5.13.??????? stream.
Would that be possible - - - please?
TIA
prev parent reply other threads:[~2021-06-23 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:25 [GIT PULL] HDMI codec improvements, v2 Maxime Ripard
2021-06-16 7:23 ` Maxime Ripard
2021-06-23 12:13 ` Maxime Ripard
2021-06-23 13:14 ` o1bigtenor [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=CAPpdf58AmzQkAQBx8x_kjfREto9qugYS0jLV+0qfp+atDFRimA@mail.gmail.com \
--to=o1bigtenor@gmail.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tzimmermann@suse.de \
/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 NNTP newsgroup(s).